Integrated home energy management, home monitoring, and automated fault mitigation

ABSTRACT

A system includes control circuitry configured to manage faults of an electrical system. The system is configured to monitor consumption for a plurality of electrical circuits, such as branch circuits, and generate device information about a device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled. The system is also configured to determining that an event has occurred based on the device information and interrupt current of the at least one electrical circuit, generate a notification, communicate a control signal to the device in response to the event occurring to mitigate the event, actuate a second device in response to the event, or a combination thereof.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present disclosure is directed to providing home energy management including fault mitigation. This application claims the benefit of U.S. Provisional Patent Application No. 63/256,403 filed Oct. 15, 2021, the disclosure of which is hereby incorporated by reference herein in its entirety.

BACKGROUND

A home or small business electrical infrastructure generally includes circuits, grouped by breaker that correspond to load types, spatially related loads, or both. The breakers are tripped over current or manual action, and thus provide some circuit protection. If a user, supplier, or other entity wants to monitor or manage operation if the circuits it may be performed at a load device, monitoring a total current flow at the electrical meter.

SUMMARY

The present disclosure is directed to an integrated approach to electrical systems, including monitoring and control. For example, in some embodiments, the present disclosure is directed to equipment having integrated components configured to be field-serviceable. In a further example, in some embodiments, the present disclosure is directed to a platform configured to monitor, control, or otherwise manage aspects of operation of the electrical system. For example, the system may monitor and control electrical loads, energy storage, generation sources, or a combination thereof to maintain power consumption within power capacity. In a further example, the system may identify faults or other events based on monitoring sensors and/or communications with smart devices, and respond to the faults or events. The response may include notifications, alerts, actuations, or other suitable actions to indicate the condition, mitigate the condition, or both.

In some embodiments, the present disclosure provides a framework for generalized automated response to faults based on sensor data. This methods and systems of the present disclosure may be applied outside of the context of energy management systems in other sensor and/or actuator/controller systems. For example, the methods and systems of the present disclosure may be applied in buildings or otherwise environments outside of the residential context (e.g., commercial or industrial facilities, schools, hospitals, or other suitable facilities).

In some embodiments, the present disclosure is directed to a method for managing faults of an electrical system. In some embodiments, the method includes monitoring power consumption for a plurality of electrical circuits, generating device information about a device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled, and determining that an event has occurred based on the device information. Based on the event, the method includes interrupting current of the at least one electrical circuit, generating and transmitting a notification, communicating a control signal to the device in response to the event occurring to mitigate the event, actuating a second device in response to the event, or performing a combination thereof. In some embodiments, communicating the control signal includes causing a change in current consumption of the device in response to determining the event has occurred.

In some embodiments, the at least one electrical circuit is a branch circuit of a panel. In some such embodiments, the method includes identifying the device as a smart appliance corresponding to the branch circuit, and generating the control signal based on the device information. In some embodiments, an energy management system, which may include one or more controllers, may be configured to monitor and control electrical circuits to implement the methods of the present disclosure.

In some embodiments, the device is a first device, and the method includes causing an actuator of a second device to be actuated in response to the event. For example, the second device operates independently from the first device. In a further device, the second device may include a branch relay, sprinkler, water valve, alarm, fan, pump, window, set of blinds, vent, lighting (e.g., emergency lighting), speaker, lock (e.g., to secure areas, devices, or otherwise access to devices), any other suitable actuator types or device types, or any combination thereof.

In some embodiments, the method includes receiving a sensor signal from at least one sensor communicatively coupled to the control circuitry, and determining the event has occurred based at least in part on the sensor signal. The at least one sensor may include, for example, smoke detectors, carbon monoxide (CO) detectors, air quality sensors, particulate sensors, barometers, ambient light sensors, temperature/humidity sensors, water flow sensors and/or leak detectors, microphones, IR and other photosensors, occupancy sensors, any other suitable sensor, or any combination thereof.

In some embodiments, the device is a smart appliance communicatively coupled to the processing circuitry. In some such embodiments, the method includes receiving data from the device, and generating the device information further based at least in part on the data. In some embodiments, the device is coupled to a branch circuit a panel and current flow to the device and/or branch circuit is monitored by processing circuitry.

In some embodiments, the method includes determining notification preferences, generating a notification for user indicative of the event based on the notification preferences, and transmitting the notification via a communication link based on the notification preferences. For example, the method may include generating and transmitting a notification or alert to a user such as a homeowner, a panel managing entity, an emergency response entity, or a combination thereof.

In some embodiments, the present disclosure is directed to a system for managing faults of an electrical system, wherein the system may be configured to implement the methods disclosed herein. The system includes one or more electrical circuits of a plurality of electrical circuits (e.g., branch circuits), and processing circuitry that may be communicatively coupled to a device such as a smart appliance. The processing circuitry is configured to monitor power consumption for the plurality of electrical circuits and generate device information about the device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled. In some embodiments, the processing circuitry is configured to determine that an event has occurred based on the device information, and interrupt current of the at least one electrical circuit, generate a notification, communicate a control signal to the device in response to the event occurring to mitigate the event, actuate a second device in response to the event, or a combination thereof.

In some embodiments, the present disclosure is directed to a non-transient computer readable medium comprising non-transitory computer readable instructions that when executed by processing circuitry (e.g., of an electrical system) implement the methods disclosed herein. In some embodiments, for example, the non-transitory computer readable instructions include instructions for implementing the methods disclosed herein to manage electrical faults and response. In some embodiments, the instructions include instructions for monitoring power consumption for a plurality of electrical circuits and generating device information about a device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled. In some embodiments, the instructions include instructions for determining that an event has occurred based on the device information and interrupting current of the at least one electrical circuit, generating a notification, communicating a control signal to the device in response to the event occurring to mitigate the event, actuating a second device in response to the event, or a combination thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure, in accordance with one or more various embodiments, is described in detail with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict typical or example embodiments. These drawings are provided to facilitate an understanding of the concepts disclosed herein and shall not be considered limiting of the breadth, scope, or applicability of these concepts. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.

FIG. 1 shows a system diagram of an illustrative electrical panel, in accordance with some embodiments of the present disclosure;

FIG. 2 shows a perspective view of an illustrative current sensor, in accordance with some embodiments of the present disclosure;

FIG. 3 shows an illustrative set of subsystems, which may be included in a power conversion device, in accordance with some embodiments of the present disclosure;

FIG. 4 shows a legend of illustrative symbols used in the context of FIGS. 5-16 ;

FIG. 5 shows a block diagram of an illustrative configuration that may be implemented for a home without distributed energy resources (e.g., such as solar, storage, or EVs), in accordance with some embodiments of the present disclosure;

FIG. 6 shows a block diagram of an illustrative configuration including an integrated power conversion unit that allows for direct DC-coupling of the output of a solar system with a DC string maximum power point tracking (MPPT) unit or module-mounted DC MPPT unit, in accordance with some embodiments of the present disclosure;

FIG. 7 shows a block diagram of an illustrative configuration including a solar inverter connected as an AC input through a circuit breaker, in accordance with some embodiments of the present disclosure;

FIG. 8 shows an illustrative configuration including an integrated power conversion unit which allows for direct DC coupling with a battery, in accordance with some embodiments of the present disclosure;

FIG. 9 shows a block diagram of an illustrative configuration including a bi-directional battery inverter coupled to an AC circuit breaker, in accordance with some embodiments of the present disclosure;

FIG. 10 shows a block diagram of an illustrative configuration including an integrated power conversion unit which can interconnect both a solar photovoltaic (PV) system and a battery system on the DC bus/link, in some embodiments of the present disclosure;

FIG. 11 shows a block diagram of an illustrative configuration including an external hybrid inverter connected to AC circuit breakers in the panel, wherein both the solar PV and battery systems operate through the external hybrid inverter, in accordance with some embodiments of the present disclosure;

FIG. 12 shows a block diagram of an illustrative configuration including an integrated power conversion unit connected to the solar PV system DC, in accordance with some embodiments of the present disclosure;

FIG. 13 shows a block diagram of an illustrative configuration including an integrated power conversion unit coupled to the battery system DC, and AC circuit breakers in the panel connected to a PV system operating through an external inverter, in accordance with some embodiments of the present disclosure;

FIG. 14 shows a block diagram of an illustrative configuration including a panel having a DC link and an integrated power conversion unit connected to the solar PV, battery systems, and an electric vehicle with on-board DC charging conversion, in accordance with some embodiments of the present disclosure;

FIG. 15 shows a block diagram of an illustrative configuration including an AC breaker connected to an electric vehicle with an on-board charger, in accordance with some embodiments of the present disclosure;

FIG. 16 shows a block diagram of an illustrative configuration including an EV DC-DC charger connected to an electric vehicle, in accordance with some embodiments of the present disclosure;

FIG. 17 shows an illustrative panel layout, in accordance with some embodiments of the present disclosure;

FIG. 18 shows an illustrative panel layout, in accordance with some embodiments of the present disclosure;

FIG. 19 shows an illustrative current sensing board, in accordance with some embodiments of the present disclosure;

FIG. 20 shows an illustrative current sensing board arrangement, including processing equipment, in accordance with some embodiments of the present disclosure;

FIG. 21 shows an illustrative power distribution and control board, in accordance with some embodiments of the present disclosure;

FIG. 22 shows an illustrative IoT module, in accordance with some embodiments of the present disclosure;

FIG. 23 shows a table of illustrative use cases, in accordance with some embodiments of the present disclosure;

FIG. 24 shows a network arrangement, in accordance with some embodiments of the present disclosure;

FIG. 25 shows a flowchart of illustrative processes that may be performed by the system, in accordance with some embodiments of the present disclosure;

FIG. 26 shows bottom, side, and front views of an illustrative electrical panel, in accordance with some embodiments of the present disclosure;

FIG. 27 shows a perspective view of an illustrative electrical panel, in accordance with some embodiments of the present disclosure;

FIGS. 28A-28D show several views of a current transformer board, in accordance with some embodiments of the present disclosure;

FIG. 29 shows a perspective view of a current transformer board, in accordance with some embodiments of the present disclosure;

FIG. 30 shows an exploded perspective view of an illustrative panel, in accordance with some embodiments of the present disclosure;

FIG. 31 shows a block diagram of a system including an illustrative electrical panel having relays, in accordance with some embodiments of the present disclosure;

FIG. 32 shows a block diagram of a system including an illustrative electrical panel having relays and shunt current sensors, in accordance with some embodiments of the present disclosure;

FIG. 33A shows a front view, FIG. 33B shows a side view, and FIG. 33C shows a bottom view of an illustrative assembly including a backing plate with branch relays and control boards installed, in accordance with some embodiments of the present disclosure;

FIG. 34 shows a perspective view and exploded view of the illustrate assembly of FIGS. 33A-33C, with some components labeled, in accordance with some embodiments of the present disclosure;

FIG. 35A shows a front view, FIG. 35B shows a side view, FIG. 35C shows a bottom view, and FIG. 35D shows a perspective view of an illustrative assembly including a backing plate with branch relays and control boards installed, a deadfront installed, and circuit breakers installed, in accordance with some embodiments of the present disclosure;

FIG. 36A shows a front view, FIG. 36B shows a side view, FIG. 36C shows a bottom view, and FIG. 36D shows a perspective view of an illustrative assembly including a backing plate with branch relays and control boards installed, a deadfront installed, and circuit breakers installed, wherein the branch relay control wires are illustrated, in accordance with some embodiment of the present disclosure;

FIG. 37A shows an exploded perspective view of the illustrative assembly of FIGS. 36A-36D, and FIG. 37B shows an exploded side view of the illustrative assembly of FIGS. 36A-36D, with some components labeled, in accordance with some embodiments of the present disclosure;

FIG. 38A shows a front view, FIG. 38B shows a side view, FIG. 38C shows a bottom view, FIG. 38D shows a perspective view, FIG. 38E shows a perspective exploded view, and FIG. 38F shows a side exploded view of an illustrative assembly including a relay housing with a main relay installed, a main breaker installed, and busbars, in accordance with some embodiments of the present disclosure;

FIG. 39 shows a perspective view of an illustrative branch relay, in accordance with some embodiments of the present disclosure;

FIG. 40 shows a perspective view of an illustrative branch relay and circuit breaker, in accordance with some embodiments of the present disclosure;

FIG. 41 shows an exploded perspective view of an illustrative panel having branch circuits, in accordance with some embodiments of the present disclosure;

FIG. 42 shows a perspective view of an illustrative installed panel having branch circuits, a main breaker, and an autotransformer, in accordance with some embodiments of the present disclosure;

FIG. 43 shows an illustrative system for managing electrical loads and sources, in accordance with some embodiments of the present disclosure;

FIG. 44 shows an illustrative graphical user interface (GUI), including an indication of system characteristics, in accordance with some embodiments of the present disclosure;

FIG. 45 shows a diagram of a system having elements for multiple-redundant control and monitoring, in accordance with some embodiments of the present disclosure;

FIG. 46 is a flowchart of an illustrative process for controlling electrical loads, in accordance with some embodiments of the present disclosure;

FIG. 47 is a flowchart of an illustrative process for modifying operation of loads and sources, in accordance with some embodiments of the present disclosure;

FIG. 48 is a block diagram of an illustrative system including an electrical panel, appliances, and sensors, in accordance with some embodiments of the present disclosure;

FIG. 49 is a flowchart of an illustrative process for detecting and responding to a fault, in accordance with some embodiments of the present disclosure;

FIG. 50 is a flowchart of an illustrative process for managing fault response, in accordance with some embodiments of the present disclosure;

FIG. 51 shows two plots illustrating electrical signatures of user behavior, in accordance with some embodiments of the present disclosure; and

FIG. 52 is a block diagram of an illustrative system including a plurality of controllers, in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION

Determination of electrical loads over time can be based on measurements (e.g., current measurements), information about what appliances are connected to each circuit, expected electrical profile behavior, any other available information. During normal usage, or emergencies, the actual electrical load of devices and circuits, as well as the capacity of electrical sources, may be determined and managed.

In some embodiments, the present disclosure is directed to a system that is capable of monitoring and managing the flow of energy (e.g., from multiple sources of energy, both AC and DC), serving multiple loads (e.g., both AC and DC, via branch circuits), communicating energy information, or any combination thereof. The system may include, for example, any or all of the components, subsystems and functionality described below. The system may include a microgrid interconnect device, for example. In some embodiments, the system may be configured to serve as a power control system (PCS) as defined in § 705.13 of the National Electric Code (2023).

In some embodiments, the system includes (1) a controllable rely and main service breaker that is arranged between the AC utility electric supply and all other generators, loads, and storage devices in a building or home.

In some embodiments, the system includes (2) an array of individual, controllable, electromechanical relays and/or load circuit breakers that are connected via an electrical busbar to the main service breaker (e.g., applies to both panel mounted or DIN rail mounted systems).

In some embodiments, the system includes (3) an array of current sensors such as, for example, solid-core or split-core current transformers (CTs), current measurement shunts, Rogowski coils, or any other suitable sensors integrated into the system for the purpose of providing a current measurement, providing a power measurement, and/or metering the energy input and output from each load service breaker. In some embodiments, for example, a relay is integrated with an attached shunt, and the relay/shunt is attached to a busbar.

In some embodiments, the system includes (4) a bidirectional power-conversion device that can convert between AC and DC forms of energy:

(a) with the ability to take multiple DC sub-components as inputs (e.g., with the same or different DC voltages);

(b) designed to mount or connect directly to the busbar (e.g., AC interface) or DIN-rail (e.g., with AC terminals); and

(c) with different size options (e.g., kVA ratings, current rating, or voltage rating).

In some embodiments, the system includes (5) processing equipment/control circuitry such as, for example, an onboard gateway computer, printed circuit board, logic board, any other suitable device configured to communicate with, and optionally control, any suitable sub-components of the system. The control circuitry may be configured:

(a) for the purpose of managing energy flow between the electricity grid and the building/home;

(b) for the purpose of managing energy flow between the various generators, loads, and storage devices (sub-components) connected to the system;

(c) to be capable of islanding the system from the electricity grid by switching the controllable main (e.g., dipole) relay off while leaving the safety and functionality of the main service breaker unaffected (e.g., energy sources and storage satisfy energy loads);

(d) to be capable of controlling each circuit (e.g., branch circuit) individually or in groups electronically and capable of controlling end-devices (e.g., appliances) through wired or wireless communication means. The groups can be on demand or predefined in response to an external system state (e.g. based on grid health, battery state of energy);

(e) for performing local computational tasks including making economic decisions for optimizing energy use (e.g., time of use, use mode);

(f) for allowing for external computational tasks to be run onboard as part of a distributed computing resource network (e.g. circuit level load predictions, weather-based predictions) that enhance the behavior of the local tasks;

(g) allowing for monitoring and control via a mobile app that can connect directly to the panel via WiFi or from anywhere in the world by connecting via the cloud. This allows for graceful operation of homeowner app in the absence of the cloud (e.g. during natural disasters);

(h) allowing for setup and configuration via a single mobile app for installers that simplifies the entire solar and storage installation process by connecting directly to the panel via WiFi or connecting through the cloud via a cellular network; and allowing suggestions of breaker naming by installer through mobile application to standardize names allowing immediate predictions of loads and improved homeowner experience from the moment of installation. For example, the application may be hosted via the cloud, or may be accessed by directly connecting with the panel.

In some embodiments, the system includes (6) communications equipment such as, for example, an onboard communication board with cellular (e.g., 4G, 5G, LTE), Zigbee, Bluetooth, Thread, Z-Wave, WiFi radio functionality, any other wireless communications functionality, or any combination thereof:

(a) with the ability to act both as a transponder (e.g., an access point), receiver, and/or repeater of signals;

(b) with the ability to interface wired or wireless with internet/cable/data service provider network equipment. For example, the equipment may include coaxial cables, fiber optic, ethernet cables, any other suitable equipment configured for wired and/or wireless communication, or any combination thereof;

(c) capable of updating software and/or firmware of the system by receiving updates over-the-air. For example, by receiving updates to applications and operating systems by downloading them via a network connection, or from a user's phone through an application, or any combination thereof; or

(d) capable of relaying software and/or firmware updates to remote components of the system contained elsewhere, inside the primary system enclosure, or outside the primary system enclosure.

Any or all of the components listed above may be designed to be field replaceable or swappable for repairs, upgrades, or both. The system includes energy-handling equipment as well as data input/output (TO) equipment.

In some embodiments, the system is configured for single phase AC operation, split phase AC operation, three-phase AC operation, or a combination thereof. In some embodiments, the system contains a neutral-forming autotransformer or similar magnetics or power electronics in order to support microgrid operation when installed with a single-phase inverter.

In some embodiments, the system contains hardware safety circuits that protect against disconnection, failure, or overload of the neutral-forming autotransformer or equivalent component by detecting and automatically disconnecting power to prevent risk of damage to appliances or fire caused by imbalanced voltage between phases.

In some embodiments, components of the system are configured for busbar mounting, DIN rail mounting, or both, for integration in electrical distribution panels. In some embodiments, the system is designed to be mechanically compatible with commercial off-the-shelf circuit breakers. In some circumstances, commercial off-the-shelf controllable breakers may be included in the panel and managed by the system's control circuitry.

A consumer, nominated service provider, or other suitable entity may monitor and control one or more breakers, relays, devices, or other components using an application or remotely controlling (e.g., from a network-connected mobile device, server, or other processing equipment).

In some embodiments, the system is installed with included (e.g., complimentary) hardware that provides controls, metering, or both for one or more downstream subpanels, communicating using wireless or powerline communications.

In some embodiments, a thermal system design allows for heat rejection from power electronics or magnetics such as neutral-forming transformers. This may be done with active cooling or passive convection.

In some embodiments, the system includes various modular power-conversion system sizes that are configured to replace circuit breakers, relays, or both (e.g., as more are needed, or larger capacity is needed).

In some embodiments, controllable relays are configured to receive a relatively low-voltage (e.g., less than the grid or load voltage) signal (e.g., a control signal) from an onboard computer.

In some embodiments, a main service breaker is also metered (e.g., by measuring current, voltage, or both). For example, metering may be performed at any suitable resolution (e.g., at the main, at a breaker, at several breakers, at a DC bus, or any combination thereof). Metering may be performed at any suitable frequency, with any suitable bandwidth, and accuracy to be considered “revenue grade” (e.g., to provide an ANSI metering accuracy of within 0.5% or better).

In some embodiments, the system is configured to determine and analyze high-resolution meter data for the purpose of disaggregation. For example, disaggregation may be performed by an entity (e.g., an on-board computer, or remote computing equipment to which energy information is transmitted via the network).

In some embodiments, the main utility service input can be provided directly or through a utility-provided meter.

In some embodiments, control of the system is divided between microprocessors, such that safety and real-time functionality features are handled by a real-time microprocessor and higher-level data analysis, networking, logic interactions, any other suitable functions, or a combination thereof are performed in a general-purpose operating system.

FIG. 1 shows illustrative system 100 for managing and monitoring electrical loads, in accordance with some embodiments of the present disclosure. System 100 may be configured for single phase AC operation, split phase AC operation, 3-phase AC operation, or a combination thereof. In some embodiments, components of system 100 are configured for busbar mounting, DIN rail mounting, or both, for integration in electrical distribution panels. In some circumstances, non-controllable breakers are included in panel 102. In some embodiments, a consumer, a nominated service provider, any other suitable entity, or any combination thereof may monitor and control one or more breakers, devices, or other components using an application or remotely (e.g., from a network-connected mobile device, server, or other processing equipment). In some embodiments, system 100 is thermally designed to allow for heat rejection (e.g., due to Ohmic heating). In some embodiments, system 100 includes one or more modular power-conversion system sizes that are configured to replace circuit breakers (e.g., as more are needed, or larger capacity is needed). In some embodiments, controllable circuit devices 114 (e.g., breakers, relays, or both) are configured to receive a relatively low-voltage (e.g., less than the grid or load voltage) control signal from an onboard computer 118 (e.g., processing equipment/control circuitry). For example, onboard computer 118 may include a wireless gateway, a wired communications interface, a display, a user interface, memory, any other suitable components, or any combination thereof. In some embodiments, main service breaker 112 is metered (e.g., be measuring current, voltage, or both). For example, metering may be performed at any suitable resolution (e.g., at the main, at a breaker, at several breakers, at a DC bus, or any combination thereof). In some embodiments, system 100 is configured to determine high-resolution meter data for the purpose of disaggregation. For example, disaggregation may be performed by an entity (e.g., an on-board computer, or remote computing equipment to which energy information is transmitted via the network). In some embodiments, main utility service input 110 is provided directly or provided through a utility-provided meter.

An AC-DC-AC bi-directional inverter may be included as part of the system of FIG. 1 but need not be. As illustrated, system 100 includes power conversion device 120 for electrically coupling DC resources. For example, power conversion device 120 (e.g., including power electronics) may have a 10 kVa rating, or any other suitable rating. DC inputs 116 may be coupled to any suitable DC devices.

In some embodiments, system 100 includes one or more sensors configured to sense current. For example, as illustrated, system 100 includes current sensors 152 and 162 (e.g., a current transformer flange or current shunt integrated into a busbar) for panel-integrated metering functionality, circuit breaker functionality, load control functionality, any other suitable functionality, or any combination thereof. Current sensors 152 and 162 each include current sensors (e.g., current transformers, shunts, Rogowski coils) configured to sense current in respective branch circuits 156 (e.g., controlled by respective breakers 154 or relays of controllable circuit devices 114, as illustrated in enlargement 150). In some embodiments, system 100 includes voltage sensing equipment, (e.g., a voltage sensor), configured to sense one or more AC voltage (e.g., voltage between line and neutral), coupled to control circuitry.

In some embodiments, panel 102 includes indicators 122 that are configured to provide a visual indication, audio indication, or both indicative of a state of a corresponding breaker of controllable circuit devices 114. For example, indicators 122 may include one or more LEDs or other suitable lights of one color, or a plurality of colors, that may indicate whether a controllable breaker is open, closed, or tripped; in what range a current flow or power lies; a fault condition; any other suitable information; or any combination thereof. To illustrate, each indicator of indicators 122 may indicate either green (e.g., breaker is closed on current can flow) or red (e.g., breaker is open or tripped).

In some embodiments, the system includes, for example, one or more low-voltage connectors configured to interface with one or more other components inside or outside the electrical panel including, for example, controllable circuit breakers, communication antennas, digital/analog controllers, any other suitable equipment, or any combination thereof.

In some embodiments, system 100 includes component such as, for example, one or more printed circuit boards configured to serve as a communication pathway for and between current sensors, voltage sensors, power sensors, actuation subsystems, control circuitry, or a combination thereof. In some embodiments, a current sensor provides a sufficient accuracy to be used in energy metering (e.g., configured to provide an ANSI metering accuracy of within 0.5% or better). In some embodiments, current sensors 152 and 162 (e.g., the current sensing component) can be detached, field-replaced, or otherwise removable. In some embodiments, one or more cables may couple a printed circuit board (PCB) of a current sensor to the processing equipment. In some embodiments, the sum of each power of the individual circuits (e.g., branch circuits) corresponds to the total meter reading (e.g., is equivalent to a whole-home “smart” meter).

In some embodiments, system 100 includes an embedded power conversion device (e.g., power electronics). The power conversion device (e.g., power conversion device 120) may be arranged in a purpose-built electrical distribution panel, allowing for DC-coupling of loads and generation (e.g., including direct coupling or indirect coupling if voltage levels are different). For example, DC inputs 116 may be configured to be electrically coupled to one or more DC loads, generators, or both. In some embodiments, power conversion device 120 includes one or more electrical breakers that snap on to one or more busbars of an electrical panel 102. For example, AC terminals of power conversion device 120 may contact against the busbar directly. In a further example, power conversion device 120 may be further supported mechanically by anchoring to the backplate of electrical panel 102 (e.g., especially for larger, or modular power stages). In some embodiments, power conversion device 120 includes a bi-directional power electronics stack configured to convert between AC and DC (e.g., transfer power in either direction). In some embodiments, power conversion device 120 includes a shared DC bus (e.g., DC inputs 116) configured to support a range of DC devices operating within a predefined voltage range or operating within respective voltage ranges. In some embodiments, power conversion device 120 is configured to enable fault-protection. For example, system 100 may prevent fault-propagation using galvanic isolation. In some embodiments, power conversion device 120 is configured to allow for digital control signals to be provided to it in real-time from the control circuitry (e.g., within electrical panel 102, from onboard computer 118).

In some embodiments, power conversion device 120 is configured as a main service breaker and utility disconnect from a utility electricity supply. For example, power conversion device may be arranged at the interface between a utility service and a site (e.g., a home or building). For example, power conversion device 120 may be arranged within electrical panel 102 (e.g., in place of, or in addition to, a main service breaker 112).

FIG. 2 shows a perspective view of illustrative current sensor 200, in accordance with some embodiments of the present disclosure. For example, current sensor 200 may be mounted to the backplate of an electrical panel in a purpose-built housing (e.g., as part of panel 102 of FIG. 1 ), mounted on a DIN-rail, or include any other suitable mounting configuration. In some embodiments, the component includes, for example, one or more solid-core current-transformers 206 configured to provide high-accuracy metering of individual load wires fed into the electrical panel and connected to circuit breakers (e.g., in some embodiments, one sensor per breaker). In some embodiments, the component includes, for example, current measurement shunts attached to, or integrated directly with, one or more bus bars. Signal leads 204 are configured to transmit sensor information (e.g., measurement signals), receive electric power for sensors, transmit communications signals (e.g., when current sensor 200 includes an analog to digital converter and any other suitable corresponding circuitry). In some embodiments, current sensor 200 is configured to sense current and transmit analog signals via signal leads 204 to control circuitry. In some embodiments, current sensor 200 is configured to sense current and transmit digital signals via signal leads 204 to control circuitry. For example, signal leads 204 may be bundled into one or more low-voltage data cables for providing breaker controls. In some embodiments, current sensor 200 is configured to sense one or more voltages, as well as current, and may be configured to calculate, for example, power measurements associated with branch circuits or other loads.

FIG. 3 shows illustrative set of subsystems 300, which may include a power conversion device (e.g. power conversion device 120 of FIG. 1 ), in accordance with some embodiments of the present disclosure. In some embodiments, the power conversion device is configured to provide galvanic isolation between the grid (e.g., AC grid 302, as illustrated) and the electrical system by converting AC to DC (e.g., using AC-DC converter 304) at the electrical main panel. In some embodiments, the power conversion device is configured to step-up from nominal DC voltage to a shared DC bus voltage (e.g., that may be compatible with inter-operable DC loads and generation). For example, DC-DC converter 306 may be included to provide isolation, provide a step up or step down in voltage, or a combination thereof. In a further example, the power conversion device may include a DC-DC isolation component (e.g., DC-DC converter 306). In some embodiments, the power conversion device is configured to convert power from DC bus voltage to nominal AC voltage to connect with conventional AC loads & generation. For example, DC-AC converter 308 may be included to couple with AC loads and generation. In some embodiments, the power conversion device is configured to support microgrid (e.g., self-consumption) functionality, providing a seamless or near seamless transition from and to grid power. In some embodiments, the self-consumption architecture benefits in terms of conversion losses associated with the double-conversion (e.g., no need to convert to grid AC during self-consumption). In some embodiments, the device is configured to support AC and DC voltages used in homes/buildings. For example, the power conversion device may be configured to support typical AC appliance voltages and DC device voltages. In some embodiments, the power conversion device may be used to support a microgrid, real-time islanding, or other suitable use-cases.

FIG. 4 shows legend 400 of illustrative symbols used in the context of FIGS. 5-16 , in accordance with some embodiments of the present disclosure.

FIG. 5 shows a block diagram of illustrative configuration 500 that may be implemented for a home without distributed energy resources (e.g., such as solar, storage, or EVs), in accordance with some embodiments of the present disclosure. As illustrated in FIG. 5 , the system includes integrated gateway 503, controllable (e.g., islanding) main service device 501 with transfer device 502, and individual circuit devices 504 that are both metered and controllable (e.g., switched). In some embodiments, the busbar design can accommodate both controllable and non-controllable (e.g., legacy) circuit devices (e.g., breakers, relays, or both). In some embodiments, branch meters 505 are configured to be modular, allowing for grouping circuits with one device (e.g., 2-4 circuits or more). In some embodiments, integrated gateway 503 is configured to perform several local energy management functions including, for example: voltage-sensing the grid; controlling islanding main service device 501 (e.g., a main breaker); controlling circuit breakers of circuit devices 504 individually and in groups, measuring power & energy in real-time from each branch, computing total power at who panel level; and communicating wirelessly (e.g., using cellular, WiFi, Bluetooth, or other standard) with external devices as well as any suitable cloud-hosted platform. The system may be configured to monitor and control various electrical loads 506. The field-installable power conversion unit (e.g., a bi-directional inverter) may be included to this configuration. In some embodiments, controllable main service device 501 with transfer device 502 is configured to be used for safely disconnecting from the grid, connecting to grid 599, or both.

FIG. 6 shows a block diagram of illustrative configuration 600 including integrated power conversion device 510 that allows for direct DC-coupling of the output of a solar system 512 with a DC string maximum power point tracking (MDPT) unit or module-mounted DC MPPT unit (e.g., unit 511), in accordance with some embodiments of the present disclosure. In some embodiments, the DC input voltage range of power conversion device 510 can accommodate various DC inputs allowing for easy integration of solar modules into a home. In some embodiments, power conversion device 510 is configured to serve as an isolation or disconnect device from the grid or electric loads. In some embodiments, the output level of solar system 512 is controllable from power conversion device 510 modulating the DC link voltage.

FIG. 7 shows a block diagram of illustrative configuration 700 including external power conversion device 513 (e.g., a solar inverter) connected as an AC input through a circuit breaker (e.g., of controllable circuit devices 504), in accordance with some embodiments of the present disclosure. In some embodiments, external power conversion device 513 may be a string MPPT or solar module mounted MPPT or micro-inverter. In some embodiments, a circuit breaker used to couple solar system 514 to the busbar of the panel may be sized to accommodate the appropriate system capacity. The output level of solar system 514 may be controlled using direct communication with solar system 514 or using voltage-based or frequency-based controls (e.g., from gateway 503). For example, frequency droop may be described as a modulation to instantaneous voltage V(t), rather than root-mean square voltage (V_RMS).

FIG. 8 shows illustrative configuration 800 including power conversion device 515 (e.g., a DC-DC converter, as illustrated) which allows for direct DC coupling with battery system 516 (i.e., an energy storage device), in accordance with some embodiments of the present disclosure. The output of battery system 516 may vary within an allowable range of DC link 517 (e.g., a DC bus). In some embodiments, the output level of battery system 516 is controllable from the integrated power conversion unit modulating the DC link voltage (e.g., an AC-DC converter).

FIG. 9 shows a block diagram of illustrative configuration 900 including bi-directional battery inverter 518 coupled via AC link 520 to an AC circuit breaker (of controllable circuit devices 504), in accordance with some embodiments of the present disclosure. In some embodiments, the charge/discharge levels of battery system 519 may be controlled either using direct communication with battery inverter 518 or through voltage-based or frequency-based control.

FIG. 10 shows a block diagram of illustrative configuration 1000 including integrated power conversion device 510 which can interconnect both a solar photovoltaic (PV) system (e.g., solar system 525) using maximum-power point tracking (MPPT) and a battery system (e.g., battery system 523) via DC link 521. In some embodiments, integrated power conversion device 510 effectively serves as a hybrid inverter embedded within the panel. Illustrative configuration 1000 of FIG. 10 may offer significant advantages in terms of direct DC charging of the battery from PV generation. In some embodiments, the illustrative configuration of FIG. 10 allows for minimizing, or otherwise reducing, the number of redundant components across power conversion, metering, and gateway/controls. In some embodiments, both the PV and battery input/output levels may be modified using voltage-based controls on the DC bus. The DC/DC converter may be provided by PV or battery vendor but may also be provided as part of the system (e.g., integrated into the system). In some embodiments, as illustrated, battery system 523 is coupled to DC-DC converter 522 and solar system 525 is coupled to DC-DC converter 524, and thus both are coupled to DC link 521, albeit operating at potentially different voltages.

FIG. 11 shows a block diagram of illustrative configuration 1100 including external hybrid inverter 527 coupled via AC link 526 to one or more of controllable circuit devices 504 in the panel, wherein both solar system 529 and battery system 528 operate through external hybrid inverter 527, in accordance with some embodiments of the present disclosure. In some embodiments, the PV output and battery charge/discharge levels may be controlled either using direct communication with hybrid inverter 527 or through voltage-based control (e.g., using gateway 503). In some embodiments, the system is configured to accommodate installation of an autotransformer. For example, the autotransformer may support a 240V hybrid inverter when the system includes a split phase 120V/240V set of loads. In some embodiments, the system is configured with hardware and/or software devices designed to protect loads from autotransformer failures, and/or protect an autotransformer from excessive loads. In some embodiments the system is configured with hardware and/or software devices designed to disconnect an inverter from the system in the event of a fault in order to protect an autotransformer and/or to protect loads. In some embodiments, the autotransformer may be controlled by, for example, controllable circuit breakers or control relays. In some embodiments hardware and/or software designed for system protection may use controllable circuit breakers or control relays to disconnect the autotransformer and or inverter from the system.

FIG. 12 shows a block diagram of illustrative configuration 1200 including integrated power conversion device 510 connected to solar PV system 532 via DC link 530 and DC-DC converter 531, in accordance with some embodiments of the present disclosure. The system also includes one or more of controllable circuit devices 504 in the panel coupled via AC link 533 to external bi-directional inverter 534, which is connected to battery system 535. Illustrative configuration 1200 of FIG. 12 may be configured to support various battery designs that are deployed with built-in bi-directional inverter 534. In some embodiments, the configuration allows for relatively easy augmentation of battery capacity on the direct DC bus (e.g., coupled to bi-directional inverter 534).

FIG. 13 shows a block diagram of illustrative configuration 1300 including integrated power conversion device 510 coupled to battery system 538 via DC-DC converter 537, and one or more of controllable circuit devices 504 in the panel coupled via AC link 539 to solar PV system 541 operating through external inverter 540, in accordance with some embodiments of the present disclosure. In some embodiments, illustrative configuration 1300 of FIG. 13 is configured to support installation where solar is already deployed. For example, it may allow for relatively easy augmentation of battery and PV capacity on the direct DC bus (e.g., DC link 536).

FIG. 14 shows a block diagram of illustrative configuration 1400 including a panel having DC link 542 and integrated power conversion device 510 connected to solar PV system 547 via DC-DC converter 546, battery system 545 coupled via DC-DC converter 544, and electric vehicle with on-board DC charging conversion system 543, in accordance with some embodiments of the present disclosure. In some embodiments, each of the systems coupled to DC link 542 may be individually monitored and controlled using direct communication or voltage-based controls, for example (e.g., from gateway 503).

FIG. 15 shows a block diagram of illustrative configuration 1500 including one or more of controllable circuit devices 504 coupled via AC link 549 to electric vehicle 550 with on-board charger 551 and onboard battery system 552, in accordance with some embodiments of the present disclosure. In some embodiments, the system may be configured to control charging/discharging of battery system 552 of electric vehicle 550 (e.g., depending on whether on-board charger 551 is bi-directional).

FIG. 16 shows a block diagram of illustrative configuration 1600 including power conversion device 510 coupled to EV DC-DC charger 554 via DC link 553, which is in turn coupled to electric vehicle 560 via DC link 555, in accordance with some embodiments of the present disclosure. For example, this may allow for circumvention of any on-board chargers (e.g., onboard charger 561) and faster, higher efficiency charging of battery system 562 of electric vehicle 560. In some embodiments, the charge/discharge levels of battery system 562 may be controlled either using direct communication with battery system 562 or through voltage-based control of DC-DC charger 554, for example. In some embodiments, the system includes an integrated DC-DC charger (e.g., integrated into power conversion device 510), configured to charge an electric vehicle directly (e.g., without an intermediate device).

FIG. 17 shows illustrative panel layout 1700, in accordance with some embodiments of the present disclosure. For example, the panel includes main breaker relay 1702 (e.g., for grid-connection), gateway board 1704 (e.g., including processing equipment, communications equipment, memory, and input/output interface), two current transformer modules 1706 and 1708 (e.g., PCBs including solid-core current sensors), and power conversion device 1710 (e.g., an AC-DC converter).

FIG. 18 shows illustrative panel layout 1800, in accordance with some embodiments of the present disclosure. For example, the panel includes main breaker relay 1802 (e.g., for grid-connection), processing equipment 1804 (e.g., IoT module 1814, microcontroller unit 1824 (MCU), and input/output (I/O) interface 1834), two current transformers modules 1806 and 1808 (e.g., PCBs including solid-core current sensors), and power conversion device 1810 (e.g., an AC-DC converter). In an illustrative example, main breaker relay 1802 and power conversion device 1810 of FIG. 18 may be controllable using processing equipment 1804 (e.g., having a wired or wireless communications coupling).

FIG. 19 shows illustrative current sensing board 1900 (e.g., with current transformers), in accordance with some embodiments of the present disclosure. For example, as illustrated, current sensing board 1900 includes connectors 1902, 1904, and 1906 for power and signal I/O, ports 1910 for coupling to controllers, LEDs 1908 or other indicators for indicating status, any other suitable components (not shown), or any combination thereof. For example, current sensing board 1900 may be included any illustrative panel or system described herein.

FIG. 20 shows illustrative current sensing board arrangement 2000, with current sensing board 2001 including processing equipment, in accordance with some embodiments of the present disclosure. For example, as illustrated, current sensing board 2001 is configured to receive signals from six current transformers at terminals 2002. In some embodiments, current sensing board 2001, as illustrated, includes general purpose input/output (GPIO) terminals 2008 and 2012 configured to transmit, receive, or both, signals from one or more other devices (e.g., a rotary breaker drive, LED drive, and/or other suitable devices). In some embodiments, current sensing board 2001, as illustrated, includes serial peripheral interface (SPI) terminals 2004, universal asynchronous receiver/transmitter terminals 2010, system activity report (SAR) terminals 2006, any other suitable terminals, or any combination thereof.

FIG. 21 shows an illustrative arrangement including board 2100 (e.g., for power distribution and control), in accordance with some embodiments of the present disclosure. For example, illustrative board 2100 includes GPIO terminals 2102, 2104, and 2106 (e.g., coupled to main AC breaker relay 2150, main AC breaker control module 2151, LED drive 2152, and IoT module 2153), serial inter-integrated circuit (I2C) communications terminals 2108 (e.g., I2C protocol for communicating with temperature sensor 2154 and authentication module 2155), a universal serial bus (USB) communications terminals 2110 (e.g., for communicating with an IoT module 2153), a real-time clock (RTC) 2112 coupled to clock 2156 (e.g., a 32 kHz clock), several serial peripheral interface (SPI) communications terminals 2114 (e.g., for communicating with current sensor boards 2157, any other suitable sensors, or any other suitable devices), and quad-SPI (QSPI) communications terminals 2116 (e.g., for communicating with memory equipment 2158). Board 2100, as illustrated, is configured to manage/monitor main AC relay 2150 and accompanying electrical circuitry that may be coupled to AC-DC converters 2160, 2161, and 2162, AC busbars 2170, or any other suitable devices/components of the system.

FIG. 22 shows an illustrative IoT module 2200, in accordance with some embodiments of the present disclosure. Illustrate IoT module 2200 includes power interface 2202 (e.g., to receive electrical power from power supply 2203), memory interface 2204 (e.g., to store and recall information/data from memory 2205), communications interfaces 2216 and 2208 (e.g., to communicate with a WiFi module 2217 or LTE module 2209), USB interface 2206 (e.g., to communicate with control MCU 2207), GPIO interface 2206 (e.g., to communicate with control MCU 2207), and QSPI interface 2210 (e.g., to communicate with memory equipment 2211 or other devices).

FIG. 23 shows table 2300 of illustrative use cases, in accordance with some embodiments of the present disclosure. For example, table 2300 includes self-generation cases (e.g., with self-consumption, import/export), islanding cases (e.g., with and without solar, battery, and EV), and a next export case (e.g., including solar, battery and EV, with net export). In some embodiments, the panels and systems described herein may be configured to achieve the illustrative use cases of table 2300.

In some embodiments, the system is configured to implement a platform configured to communicate with HMI devices (e.g., Echo™, Home™, etc.). In some embodiments, the system may be configured to serve as a gateway for controlling smart appliances enabled with compatible wired/wireless receivers. For example, a user may provide a command to an HMI device or to an application, which then sends a direct control signal (e.g., a digital state signal) to a washer/dryer (e.g., over PLC, WiFi or Bluetooth).

In some embodiments, the platform is configured to act as an OS layer, connected to internal and external sensors, actuators, both. For example, the platform may allow for third party application developers to build features onto or included in the platform. In a further example, the platform may provide high-resolution, branch level meter data for which a disaggregation service provider may build an application on the platform. In a further example, the platform may be configured to control individual breakers, and accordingly a demand-response vendor may build an application on the platform that enables customers to opt-in to programs (e.g., energy-use programs). In a further example, the platform may provide metering information to a solar installer who may provide an application that showcases energy generation & consumption to the consumer. The platform may receive, retrieve, store, generate, or otherwise manage any suitable data or information in connection with the system. In some embodiments, for example, the platform may include a software development kit (SDK), which may include an applications programming interface (API), and other aspects developers may use to generate applications. For example, the platform may provide libraries, functions, objects, classes, communications protocols, any other suitable tools, or any combination thereof.

In some embodiments, the systems disclosed herein are configured to serve as a gateway and platform for an increasing number of connected devices (e.g., appliances) in a home or business. In some embodiments, rather than supporting only a handful of ‘smart’ appliances in a home (e.g., sometimes with redundant gateways, cloud-based platforms, and applications), the systems disclosed herein may interface to many such devices. For example, each powered device in a home may interface with the electrical panel of the present disclosure, through an application specific integrated circuit (ASIC) that is purpose-built and installed with or within the appliance. The ASIC may be configured for communication and control from the panel of the present disclosure.

In some embodiments, the system provides an open-access platform for any appliance to become a system-connected device. For example, the panel may be configured to serve as a monitoring and control hub. By including integration with emerging HMI (human-machine interface) solutions and communication pathways, the system is configured to participate in the growing IoT ecosystem.

FIG. 24 shows illustrative network arrangement 2400 (e.g., that may include an IoT arrangement), in accordance with some embodiments of the present disclosure. The systems disclosed herein may be installed in many locations (e.g., indicated by houses 2401 in FIG. 24 ), each including a respective main panel, solar panel system 2402, battery system 2404, set of appliances 2406 (e.g., smart appliances or otherwise), other loads 2408 (e.g., lighting, outlets, user devices), electric vehicle charging station 2410, one or more HMI devices 2412, any other suitable devices, or any combination thereof. The systems may communicate with one another, communicate with a central processing server (e.g., platform 2450), communicate with any other suitable network entities, or any combination thereof. For example, network entities providing energy services, third-party IoT integration, and edge computing may communicate with, or otherwise use data from, one or more systems. In some embodiments, a respective energy management system module may be associated with each of houses 2401 and/or other suitable facilities or energy systems. For example, platform 2450 may be configured to receive data, notifications, and other suitable information from houses 2401, provide information (e.g., reference information), settings, and limits to houses 2401, or a combination thereof.

In some embodiments, the system may be configured to communicate with low-cost integrated circuits, ASIC (application specific integrated circuits), PCBs with ASICs mounted onboard, or a combination thereof that may be open-sourced or based on reference designs, and adopted by appliance manufacturers to readily enable communication and controls with the systems disclosed herein. For example, the system (e.g., a smart panel or other suitable energy management system) may be configured to send/receive messages and control states of appliances to/from any smart device or device that otherwise includes an IoT module. In an illustrative example, an oven can become a smart appliance (e.g., a system-connected device) by embedding an IoT module. Accordingly, when a customer using a smart panel inputs a command (e.g., using an application hosted by the system) to set the oven to 350 degrees, the system may communicate with the module-enabled oven, transmitting the command. In a further example, the system may be configured to communicate with low-cost DC/DC devices, ASICs, or both that can be embedded into solar modules, battery systems, or EVs (e.g., by manufacturers or aftermarket) that allow control of such devices (e.g., through DC bus voltage modulation/droop curve control). In some embodiments, each of houses 2401 may include a controller of a constellation of controllers for providing energy management.

FIG. 25 shows a flowchart of illustrative processes 2500 that may be performed by the system. For example, processes 2500 may be performed by any suitable processing equipment/control circuitry described herein.

In some embodiments, at step 2502, the system is configured to measure one or more currents associated with the electrical infrastructure or devices. For example, the system may include one or more current sensor boards configured to measure currents.

In some embodiments, at step 2504, the system is configured to receive user input (e.g., from a user device or directly to a user input interface). For example, the system may include a communications interface and may receive a network-based communication from a user's mobile device. In a further example, the system may include a touchscreen and may receive haptic input from a user.

In some embodiments, at step 2506. the system is configured to receive system information. For example, the system may receive usage metrics (e.g., peak power targets, or desired usage schedules). In a further example, the system may receive system updates, driver, or other software. In a further example, the system may receive information about one or more devices (e.g., usage information, current or voltage thresholds, communications protocols that are supported). In some embodiments, the system is configured to update firmware on connected or otherwise communicatively coupled devices (e.g., the inverter, battery, downstream appliances, or other suitable devices).

In some embodiments, at step 2508, the system is configured to receive input from one or more devices. For example, the system may include an I/O interface and be configured to receive power line communications (PLC) from one or more devices. For example, an appliance may include one or more digital electrical terminals configured to provide electricals signals to the system to transmit state information, usage information, or provide commands. Device may include solar systems, EV charging systems, battery systems, appliances (e.g., smart appliances), user devices, any other suitable devices, or any combination thereof.

In some embodiments, at step 2510, the system is configured to process information and data that it has received, gathered, or otherwise stores in memory equipment. For example, the system may be configured to determine energy metrics such as peak power consumption/generation, peak current, total power consumption/generation, frequency of use/idle, duration of use/idle, any other suitable metrics, or any combination thereof. In a further example, the system may be configured to determine an energy usage schedule, disaggregate energy loads, determine a desired energy usage schedule, perform any other suitable function, or any combination thereof. In a further example, the system may be configured to compare usage information (e.g., current) with reference information (e.g., peak desired current) to determine an action (e.g., turn off breaker).

In some embodiments, at step 2512, the system is configured to store energy usage information in memory equipment. For example, the system may store and track energy usage over time. In a further example, the system may store information related to fault events (e.g., tripping a breaker or a main relay).

In some embodiments, at step 2514, the system is configured to transmit energy usage information to one or more network entities, user devices, or other entities. For example, the system may transmit usage information to a central database. In a further example, the system may transmit energy usage information to an energy service provider.

In some embodiments, at step 2516, the system is configured to control one or more controllable breakers, relays, or a combination thereof. For example, the breakers, relays, or both may be coupled to one or more busbars, and may include a terminal to trip and reset the breaker that is coupled to processing equipment. Accordingly, the processing equipment may be configured to turn breakers, relays or both “on” or “off” depending on a desired usage (e.g., a time schedule for usage of a particular electrical circuit), a safety state (e.g., an overcurrent, near overcurrent, or inconsistent load profile), or any other suitable schedule.

In some embodiments, at step 2518, the system is configured to control one or more controllable main breakers. For example, the main breaker may be coupled to an AC grid or meter and may include a terminal to trip and reset the breaker that is coupled to processing equipment. The processing equipment may turn the breaker on or off depending on safety information, user input, or other information.

In some embodiments, at step 2520, the system is configured to schedule energy usage. For example, the system may determine a desired energy usage schedule based on the actual usage data and other suitable information. In a further example, the system may use controllable breakers, IoT connectivity, and PoL connectivity to schedule usage.

In some embodiments, at step 2522, the system is configured to perform system checks. For example, the system may be configured to test breakers, check current sensors, check communications lines (e.g., using a lifeline or ping signal), or perform any other function indicating a status of the system.

In some embodiments, at step 2524, the system is configured to provide output to one or more devices. For example, the system may be configured to provide output to an appliance (e.g., via PLC, WiFi, or Bluetooth), a DC-DC converter or DC-AC inverter (e.g., via serial communication, ethernet communication, WiFi, Bluetooth), a user device (e.g., a user's mobile smart phone), an electric vehicle charger or control system thereof, a solar panel array or control system thereof, a battery system or control system thereof.

In an illustrative example of processes 2500, the system may manage electrical loads by sensing currents, determining operating parameters, and controlling one or more breakers. The system (e.g., control circuitry thereof, using one or more current sensing modules thereof) may sense a plurality of currents. Each current of the plurality of currents may correspond to a respective controllable breaker. The system determines one or more operating parameters and controls each respective controllable breaker based on the current correspond to the respective controllable breaker and based on the one or more operating parameters.

In an illustrative example of processes 2500, the one or more operating parameters may include a plurality of current limits each corresponding to a respective current of the plurality of currents. If the respective current is greater than the corresponding current limit, the system may control the respective controllable breaker by opening the respective controllable breaker.

In an illustrative example of processes 2500, the one or more operating parameters may include a load profile including a schedule for limiting a total electrical load. The system may control each respective controllable breaker further based on the load profile.

In an illustrative example of processes 2500, the one or more operating parameters may include temporal information. The system may control each respective controllable breaker further based on the temporal information. For example, the temporal information may include an on-off time schedule for each breaker (e.g., which may be based on the measured load in that branch circuit), duration information (e.g., how long a branch circuit will be left on), any other suitable temporal information, an estimated time remaining (e.g., during operation on battery power, or until a pre-scheduled disconnect), or any combination thereof.

In an illustrative example of processes 2500, the system may (e.g., at step 2510) detect a fault condition and determine the one or more operating parameters based on the fault condition. For example, the system may determine a faulted current (e.g., based on measured currents from step 2502), receive a fault indicator (e.g., from user input at step 2504), receive a fault indicator from a network entity (e.g., from system information at step 2506), receive a fault indicator from another device (e.g., from step 2508), determine a faulted condition in any other suitable manner, or any combination thereof.

FIGS. 26-30 show illustrative views and components of electrical panel 2600, in accordance with some embodiments of the present disclosure. For example, electrical panel 2600 is an illustrative example of system 100 of FIG. 1 , which may be used to implement any of the illustrative configurations shown in FIGS. 5-16 .

FIG. 26 shows bottom, side, and front views of illustrative electrical panel 2600, in accordance with some embodiments of the present disclosure. FIG. 27 shows a perspective view of illustrative electrical panel 2600, in accordance with some embodiments of the present disclosure. Electrical panel 2600, as illustrated, includes:

antennae enclosure 2602 (e.g., configured for housing an antennae for receiving/transmitting communications signals);

gateway 2604 (e.g., control circuitry);

dead-front 2606 (e.g., to provide a recognizable/safe user interface to breakers); power module 2608 (e.g., for powering components of electrical panel 2600 with AC, DC, or both);

main breaker 2610 (e.g. controllable by gateway 2604);

main relay 2612 (e.g., for controlling main power using gateway 2604);

controllable circuit breaker(s) 2614 (e.g., for controlling branch circuits);

sensor boards 2616 and 2617 (e.g., for measuring current, voltage, or both, or characteristics thereof, electrical panel 2600 includes two sensor boards);

inner load center 2618 (e.g., including busbars and back-plane); and

power electronics 2620 (e.g., for generating/managing a DC bus, for interfacing to loads and generation).

In some embodiments, inner load center 2618 of electrical panel 2600 is configured to accommodate a plurality of controllable circuit breakers 2614, wherein each breaker is communicatively coupled to gateway 2604 (e.g., either directly or via an interface board). As illustrated, electrical panel 2600 includes inner enclosure 2650 and outer enclosure 2651. Outer enclosure 2651 may be configured to house power electronics 2620 and any other suitable components (e.g. away from usual access by a user for safety considerations). In some embodiments, inner enclosure 2650 provides access to breaker toggles for a user, as well as access to a user interface of gateway 2604. To illustrate, conductors (e.g., two single phase lines 180 degrees out of phase and a neutral, three-phase lines and a neutral, or any other suitable configuration) from a service drop may be routed to the top of electrical panel 2600 (e.g., an electric meter may be installed just above panel 2600), terminating at main breaker 2610. Each line, and optionally neutral, is then routed to main relay 2612, which controls provision of electrical power to/from inner load center 2618 (e.g., busbars thereof). Below main relay 2612, each line is coupled to a respective busbar (e.g., to which controllable circuit breakers 2614 may be affixed). In some embodiments, a bus bar may include or be equipped with current sensors such as shunt current sensors, current transformers, Rogowski coils, any other suitable current sensors, or any combination thereof. The neutral may be coupled to a terminal strip, busbar, or any other suitable distribution system (e.g., to provide a neutral to each controllable circuit breaker, branch circuit, current sensor, or a combination thereof). Sensor boards 2616 and 2617, as illustrated, each include a plurality of current sensors (e.g., each branch circuit may have a dedicated current sensor). Sensor boards 2616 and 2617 may output analog signals, conditioned analog signals (e.g., filtered, amplified), digital signals (e.g., including level shifting, digital filtering, of electrical or optical character), any other suitable output, or any combination thereof.

FIGS. 28A-28D shows several views of sensor board 2616 (e.g., sensor board 2617 may be identical, similar, or dissimilar to sensor board 2616), in accordance with some embodiments of the present disclosure. FIG. 29 shows a perspective view of sensor board 2616, in accordance with some embodiments of the present disclosure. In reference to FIG. 28A shows a top view of sensor board 2616, FIG. 28B shows a side view of sensor board 2616, FIG. 28C shows an end view of sensor board 2616, and FIG. 28D shows a bottom view of sensor board 2616. As illustrated, sensor board 2616 includes PCB 2691, PCB support 2692 affixed to PCB 2691, current sensors 2690 affixed to PCB 2691, indicators 2696 (e.g., LED indicators), controller ports 2693, power and I/O port 2694, and power and I/O port 2695. Each current sensor of current sensors 2690 includes a passthrough to accommodate a line or neutral to sense current. For example, each current sensor of current sensor 2690 may correspond to a branch circuit. In some embodiments, power and I/O ports 2694 and 2695 are configured to be coupled to other sensor boards (e.g., sensor board 2617), a power supply (e.g., power module 2608), gateway 2604, any other suitable components, or any combination thereof. In some embodiments, controller port 2693 is configured to interface to control circuitry (e.g., of gateway 2604 or otherwise) to receive/, transmit, or both, communications signals. In some embodiments, ports 2693, 2694, and 2695 are configured to communicate analog signals, electric power (e.g., DC power), digital signals, or any combination thereof.

FIG. 30 shows an exploded perspective view of illustrative electrical panel 2600 (i.e., exploded panel 3000), in accordance with some embodiments of the present disclosure. Electrical panel 3000 more clearly illustrates components of electrical panel 2600.

Some illustrative aspects of the systems described herein are described below. For example, any of the illustrative systems, components, and configurations described in the context of FIGS. 1-22, 24, and 26-30 may be used to implement any of the techniques, processes, and use cases described herein.

In some embodiments, the system (e.g., system 100 of FIG. 1 ) is configured for grid health monitoring; managing energy reserves and power flow; and integrating ATS/disconnect functionality into a panel. A circuit breaker panelboard may be designed for connection to both a utility grid as well as a battery inverter or other distributed energy resource, and may include one or more switching devices on the circuit connecting the panelboard to the utility point of connection, one or more switching devices on the branch circuits serving loads, any other suitable components, or any combination thereof. In some embodiments, the system includes voltage measurement means connected to all phases of the utility grid side of the utility point of connection circuit switching device, which are in turn connected to logic circuitry capable of determining the status of the utility grid. In some embodiments, the system includes one or more logic devices (e.g., control circuitry of a gateway) capable of generating a signal to cause the switching device (e.g., main relay 2612 of FIG. 26 ) to disconnect the panelboard from the utility grid when the utility grid status is unsuitable for powering the loads connected to the panelboard, thereby forming a local electrical system island and either passively allows or causes the distributed energy resource to supply power to this island (e.g., using electrical signaling or actuation of circuit connected switching devices). In some embodiments, the system includes a preprogrammed selection of branch circuits, which are capable of being disabled when the local electrical system is operating as an island, in order to optimize energy consumption or maintain the islanded electrical system power consumption at a low enough level to be supplied by the distributed energy resource. In some embodiments, the system executes logic that generates and/or uses forecasts of branch circuit loads, appliance loads, measurements of branch circuit loads (e.g., based on signals from a sensor board), or a combination thereof to dynamically disconnect or reconnect branch circuits to the distributed energy resource, send electrical signals to appliances on branch circuits enabling or disabling them in order to optimize energy consumption, maintain the islanded electrical system power consumption at a low enough level to be supplied by the distributed energy resource, or a combination thereof. In some embodiments, the system includes an energy reservoir device such as, for example, one or more capacitors or batteries, capable of maintaining logic power and switching device actuation power in the period after the utility grid point of connection circuit switching device has disconnected the electrical system from the utility grid, and before the distributed energy resource begins to supply power to the islanded electrical system, in order to facilitate actuation of point of connection and branch circuit switching devices to effect the aforementioned functions.

In some embodiments, the system (e.g., system 100 of FIG. 1 ) is configured to provide hardware safety for phase imbalance or excessive phase voltage in a panelboard serving an islanded electrical system. In some embodiments, the system includes a circuit breaker panelboard (e.g., panel 2600 of FIG. 26 ) designed for connection to a battery inverter or other distributed energy resource. The panelboard may be configured to operate in islanded mode, with the served AC electrical system disconnected from any utility grid. In some embodiments, a distributed energy resource supplying power to the panelboard is connected using fewer power conductors (hereafter “conductors”) than the electrical system served by the panelboard. The panelboard may include a transformer or autotransformer, or be designed for connection to a transformer or autotransformer provided with at least one set of windings with terminals equal in number to the number of conductors of the electrical system served by the panelboard. In some embodiments, the transformer is designed to receive power from a connection including the same number of power conductors as the connection to the distributed energy resource.

In some embodiments, a panelboard includes a plurality of electronic hardware safety features and a plurality of electrical switching devices (e.g., controllable relays and circuit breakers). For example, the safety features may be designed to monitor either the difference in voltage of all of the power conductors of the supplied electrical system, designed to monitor the difference in voltage of each of the conductors of the electrical system with respect to a shared return power conductor (“neutral”), or both. The system (e.g., control circuitry thereof) may monitor voltages, hereafter termed “phase voltages,” or a suitable combination of monitoring of difference in voltages and phase voltages such that the power supply voltage to all devices served by the electrical system is thereby monitored.

In some embodiments, the system (e.g., system 100 of FIG. 1 ) includes safety features configured to maintain a safe state when subjected to a single point component or wiring fault. For example, the safety features may be configured to entirely break the connection between the distributed energy resource and the panelboard if conditions that could lead to excessive voltages being supplied to any load served by the panelboard are detected. In a further example, a panelboard connected to a 240V battery inverter having two terminals with corresponding conductors. In some embodiments, the panelboard includes an autotransformer having two windings and three terminals, and is configured to serve an islanded electrical system of the 120V/240V split phase type. This configuration, for example, includes three conductors that are used to supply two 120V circuits with respect to a shared neutral conductor, each of the 120V conductors being supplied with power 180 degrees out of phase with respect to the other. In some such embodiments, the panelboard includes one or more of the following:

(1) A single phase 240V battery inverter containing an overvoltage detection circuit, which disables output of the inverter when excessive voltages are detected.

(2) A central voltage imbalance detector circuit, which sends a signal when an imbalance in phase voltage is detected.

(3) Two separate actuation circuits associated with two separate switching devices, each switching device being in circuit with the battery inverter.

(4) Two voltage amplitude detector circuits, one associated with each switching device, and each monitoring one phase of the electrical system.

(5) Actuation circuits configured to disconnect the associated switching device if either the central voltage imbalance detector signal is transmitted, or an excessive voltage associated with the monitored electrical system phase is detected, or if the logic power supply to the actuation circuit is lost.

(6) Optionally, an energy reservoir associated with each actuation circuit, to enable each actuation circuit to take the action needed to disconnect the switching device after loss of logic power supply to the actuation circuit, especially if the switching device is bi-stable.

In some embodiments, the system (e.g., system 100 of FIG. 1 ) includes a plurality of metering circuits connected to control circuitry (e.g., a gateway) that monitor current transducers associated with one busbar (e.g., included in a sensor board). In some embodiments, an electrical panelboard includes at least one power distribution conductor (hereafter “bus bar” and referring to any rigid or flexible power distribution conductors) that distributes power to multiple branch circuits. For example, each branch circuit may include one or more current transducers such as current measurement shunts, non-isolated current transformers, non-isolated Rogowski coils, any other suitable current sensor, or any combination thereof (e.g., using sensor board 2616 of FIG. 26 or any other suitable sensor system). In some embodiments, all branch circuits associated with a given bus bar are monitored by a plurality of metering circuits that each measure current or power associated with a given branch circuit or set of branch circuits (e.g., using sensor board 2616 of FIG. 26 or any other suitable sensor system). The metering circuits may be connected together without need for galvanic isolation, and the metering circuits may include, for example, a system of common mode filters, differential amplifiers, or both. For example, metering circuits including one or more filters or filter systems may be able to produce accurate results from the signals generated by the current transducers even in the presence of transient or steady state voltage differences existing between the transducers of each branch circuit served by the bus bar. Such differences may result from voltage differences associated with current flow through the resistive or inductive impedance of the bus bar and branch circuit system, and may be coupled to the current transducers either by direct galvanic connection or capacitive coupling, parasitic or intentional.

In the present disclosure, “non-isolated” is understood to mean the condition which exists between two electrical conductors either when they are in direct electrical contact, or when any insulation or spacing between them is of insufficient strength or size to provide for the functional or safety design requirements which would be needed if one of the conductors were energized by an electric potential associated with a conductor in the electrical system served by the panelboard, and the other conductor were to be either left floating, or connected to a different potential served by the electrical system.

In some embodiments, metering circuits (e.g., which transmit sensor signals) share a common logic or low voltage power supply system. In some embodiments, metering circuits share a non-isolated communication medium. In some embodiments, metering circuits are collocated on a single printed circuit board (e.g., sensor board 2616 of FIG. 26 ), which is physically close to the bus bar and is sized similarly in length to the bus bar, and in which a printed low voltage power distribution conductor associated with the metering circuits is electrically connected to the bus bar at a single central point, near the middle of the length of the bus bar. In some embodiments, a power supply system is galvanically bonded to the bus bar at one or more points.

In some embodiments, a system (e.g., system 100 of FIG. 1 ) includes an electrical connection to the bus bar that is made using a pair of resistance elements (e.g., resistors) connected between the printed power distribution conductor and each of the leads associated with a single current measurement shunt type of current transducer (e.g., which each serve one of the branch circuits). For example, the transducer may be arranged near the middle of the length of the bus bar. Further, the resistance elements may be sized such that any current flow through them caused by the potential drop across the shunt transducer is negligible in comparison to the resistance of the shunt and the resistances of any connecting conductors that connect the shunt to the resistances, so as not to materially affect the signal voltage produced by the transducer when said current flows.

In some embodiments, a pair of systems (e.g., two instances of system 100 of FIG. 1 , which may be but need not be similarly configured) as have been previously described are included, with one system being associated with each line voltage bus bar of a split phase 120V/240V electrical panelboard. In some embodiments, each of the systems is connected to a central communication device or computing device (e.g., including control circuitry) by means of a galvanically isolated communications link, and in which each system is served by a separate, galvanically isolated power supply

FIG. 31 shows a block diagram of a system including illustrative electrical panel 3110 having relays, in accordance with some embodiments of the present disclosure. An AC source, such as an AC service drop 3101 includes one or more electrical conductors configured to transmit AC power. As illustrated in FIG. 31 , service drop 3101 includes a neutral (e.g., a grounded neutral), a first line (e.g., L1 that is 120 VAC), and a second line (e.g., L2 that is 120 VAC and 180 degrees out of phase with L1). The service drop lines are coupled to electrical meter 3102, which is configured to sense, record, or both electrical power usage and generation. For example, electrical meter 3102 may include current and voltage sensors that are used to determine usage. The L1 and L2 lines are coupled to main contactor 3111, which is used to disconnect components of electrical panel 3110 from AC service drop 3101 (e.g., for safety, service, or component installation). For example, as illustrated, main contactor 3111 may be a two pole, single throw contactor, configured to disconnect both L1 and L2 from the rest of electrical panel 3110. Main relays 3112 and 3122 are configured to couple respective L1 and L2 to respective busbars 3113 and 3123. In some embodiments, main relays 3112 and 3122 are communicatively coupled to control circuitry 3130, and accordingly may be actuated open or closed by control circuitry 3130. For example, main relays 3112 and 3122 may include control terminals configured to be coupled to control circuitry 3130, and current carrying terminals configured to conduct current from L1 and L2. Main relays 3112 and 3122 may include, for example, solenoid-based relays, solid state relays, any other suitable type of relay, or any combination thereof. Busbars 3113 and 3123 are each configured to interface to a coupled to a plurality of relays and sensors, which in turn are coupled to corresponding circuit breakers. In some embodiments, busbars 3113 and 3123 distribute lines L1 and L2 to a plurality of respective relays 3114 and 3124 having integrated current sensors. For example, busbar 3113 may be engaged with a plurality of relays 3114 having a measurement current shunt included. Voltage measurement leads may be coupled to the current shunt (e.g., having a known and precise resistance or impedance), and also coupled to control circuitry 3130 for voltage measurements (e.g., real-time voltage measurements across the respective shunts to determine real-time current flow). In an illustrative example, the current shunt may include a strip of metal having a precise geometry, or otherwise precisely known electrical resistance. In some embodiments, control circuitry 3130 is configured to open and close relays 3114 and 3124, as well as read voltage drops across current shunts. Breakers 3115 and 3125 may include circuit breakers configured to provide mechanical circuitry breaking, or manual circuit breaking. For example, breakers 3115 and 3125 are accessible by a user to reset, shut off, and observe (e.g., observe if tripped). Breakers 3115 engage with relays 3114 and breakers 3125 engage with relays 3124. The output of breakers 3115 and 3125 are lines L1 and L2, available to be coupled to the wiring and load of the site (e.g., load 3140), for example.

In an illustrative example, referencing FIG. 31 , electrical panel 3110 may be a “main” panel for a residence. The electrical utility may provide, manage or specify requirements of service drop 3101 (or distribution lines coupled thereto), electrical meter 3102 (e.g., record usage from meter 3102 at some schedule), or both. Electrical panel may include main contractor 3111 near the top of the panel, with main relays 3112 and 3122 arranged behind (e.g., deeper into the wall, as viewed by a user) main contactor 3111.

In an illustrative example, referencing FIG. 31 , electrical panel 3110 may be retrofitted into a residential electrical system, displacing a conventional panel. In some embodiments, main contactor 3111 (or main breaker in some embodiments), main relays 3112 and 3122, busbars 3113 and 3123, and branch relays 3114 and 3124, are installed on a backing plate. In some such embodiments, a dead-front panel is installed to cover the relay components and busbars, with only bus bar tabs exposed thus providing access for breakers to be engaged with the relay-switched busbars.

In some embodiments, one or more relays are included in a panel, and are controllable by control circuitry 3130. In some such embodiments, the system is configured for mechanical circuit breaking (e.g., from circuit breakers), controlled circuit breaking (e.g., from relays), circuit shut-off and reset (e.g., from circuit breakers, relays, or both), or a combination thereof. For example, a user may interact with electrical panel 3110 manually (e.g., by opening or closing breakers), via an integrated user interface (e.g., a touchscreen or touchpad), via a software application (e.g., installed on a smart phone or other user device), or any combination thereof.

FIG. 32 shows a block diagram of system 3200 including an illustrative electrical panel having relays 3230 and 3231, and shunt current sensors 3220 and 3221, in accordance with some embodiments of the present disclosure. As illustrated, system 3200 includes main breaker 3201, main current sensors 3202, main relay 3203, lines 3204 and 3205 (e.g., L1 and L2), shunt current sensors 3220 and 3221, relays 3230 and 3231, breakers 3240 and 3241, shunt current sensors 3290 and 3291, relays 3297 and 3292, breakers 3298 and 3293, autotransformer 3299, inverter 3294, relay drive override 3280, and phase imbalance monitor 3270.

A first branch includes line 3204 (e.g., L1), with shunt current sensors 3220, relays 3230, and breakers 3240 coupled in series for each branch circuit. Similarly, a second branch includes line 3205 (e.g., L2), with shunt current sensors 3221, relays 3231, and breakers 3241 coupled in series for each branch circuit. Also coupled to lines 3204 and 3205 are shunt current sensors 3290, relays 3297, breakers 3298, and autotransformer 3299, as well as shunt current sensors 3291, relays 3292, breakers 3293, and inverter 3294. Relay driver override 3280 is coupled to each of relays 3297, 3292, and phase imbalance monitor 3270.

FIGS. 33A-42 show illustrative examples of components and aspects of an electrical panel, in accordance with some embodiments of the present disclosure. For example, the illustrative components shown in FIGS. 33A-42 may be included in an electrical panel such as electrical panel 3110 of FIG. 31 , electrical panel 3200 of FIG. 32 , or any other suitable electrical panel.

FIG. 33A shows a front view, FIG. 33B shows a side view, and FIG. 33C shows a bottom view of an illustrative assembly including a backing plate with branch relays and control boards installed, in accordance with some embodiments of the present disclosure. FIG. 34 shows perspective view 3400 and exploded view 3450 of the illustrate assembly of FIGS. 33A-33C, with some components labeled, in accordance with some embodiments of the present disclosure. As illustrated, eight branch relays 3310 are installed on backing plate 3303 (e.g., in a 4×2 arrangement), with first terminal 3312 of each branch relay 3310 secured to a busbar (e.g., busbar 3301 or busbar 3302), and second terminal 3311 of each branch relay 3310 extending outwards (e.g., in the side view, towards a user to the left). For example, as illustrated first terminals 3312 are secured by threaded fasteners (e.g., nuts threaded onto studs such as pem studs). A plurality of wires 3355 connect branch relays 3310 to corresponding connectors 3356 of a corresponding control board (e.g., control board 3350 or control board 3351, although in some embodiments, a single board may be used). For example, wires 3355 may be configured to transmit control signals from control boards 3350 and 3351 to each relay 3310 to cause the relay to open or close a circuit. In a further example, wires 3355 may be configured to transmit sensor signals (e.g., voltage signals) from a current shunt integrated into each relay 3310 to control boards 3350 and 3351 (e.g., which may determine current based on the voltage drop across the shunt). In some embodiments, backing plate 3303 is configured to be mounted to an electrical enclosure, to a building structure, included in an electrical assembly, or a combination thereof. As illustrated, each of control boards 3350 and 3351 includes four connectors 3356, although any suitable number of control boards may be included (e.g., one, two, or more than two, and each control board may include any suitable number of connectors, electrical terminals, or electrical interfaces. As illustrated in FIG. 34 , second terminals 3311 are also referred to herein as “branch breaker tabs,” control boards 3350 and 3351 are also referred to herein as “Column PCBs” or control circuitry, and backing plate 3303 is also referred to herein as a “main bus housing.” In some embodiments, each of control boards 3350 and 3351 may be electrically coupled to a central controller, which may include control circuitry, a user interface, a communications interface, memory, any other suitable components, or any combination thereof. For example, each of control boards 3350 and 3351 may be connected via a cable (e.g., having suitable terminating connectors), terminated wires, or both to the controller. As illustrated in FIG. 34 , main busbars 3301 and 3302 are included, which may correspond to two different AC lines (e.g., L1 and L2 of a utility service drop). It will be understood that although shown as coupled to control boards 3350 and 3351, wires 3355 that are coupled to branch relays 3310 may be coupled to a central controller having control circuitry, and accordingly control boards 3350 and 3351 need not be included. Control boards 3350 and 3351 may include control circuitry, be installed intermediately between branch relays 3310 and a central controller, or may be omitted entirely. It will be understood that control boards 3350, 3351, or both may provide any suitable functionality and may include, for example, a current sensing board, a sensor board, and interface board, a PCB, any other suitable control circuitry, or any combination thereof. For example, a control board may be configured to receive sensor signals, provide control signals, execute a feedback control loop, condition signals (e.g., amplify, filter, or modulate), convert signals, generate signals, manage electric power, receive and transmit digital signals, any other suitable function, or any combination thereof. It will be understood that a control board may provide any suitable functionality and may include, for example, a current sensing board, a sensor board, and interface board, a PCB, any other suitable control circuitry, or any combination thereof. For example, a control board may be configured to receive sensor signals, provide control signals, execute a feedback control loop, condition signals (e.g., amplify, filter, or modulate), convert signals, generate signals, manage electric power, receive and transmit digital signals, any other suitable function, or any combination thereof.

FIG. 35A shows a front view, FIG. 35B shows a side view, FIG. 35C shows a bottom view, and FIG. 35D shows a perspective view of an illustrative assembly including backing plate 3303 with branch relays 3310 and control boards 3350 and 3351 installed, deadfront 3330 installed, and circuit breakers 3320 installed, in accordance with some embodiments of the present disclosure. Circuit breakers 3320 engage with second terminals 3311 of branch relays 3310 to create a branch circuit.

FIG. 36A shows a front view, FIG. 36B shows a side view, FIG. 36C shows a bottom view, and FIG. 36D shows a perspective view of an illustrative assembly including backing plate 3303 with branch relays 3310 and control boards 3350 and 3351 installed, deadfront 3330 installed, and circuit breakers 3320 installed, wherein the branch relay sensor and control wires 3357 are illustrated, in accordance with some embodiment of the present disclosure. As illustrated, the assembly of FIGS. 36A-36D is the same as the assembly of FIGS. 35A-35D, with sensor and relay control wires 3357 added in FIGS. 36A-36D. For example, each branch relay 3310 may include three control terminals, configured to allow two-way actuation of the control coil (e.g., for solenoid actuated relays). In some embodiments, the sensing wires and relay control wires 3357 (e.g., from the current shunt and sense pins and actuator pins) may be, but need not be, terminated at a single connector. For example, as illustrated, a single connector 3356 is included for each branch relay 3310.

FIG. 37A shows an exploded perspective view of the illustrative assembly of FIGS. 36A-36D, and FIG. 37B shows an exploded side view of the illustrative assembly of FIGS. 36A-36D, with some components labeled, in accordance with some embodiments of the present disclosure. In some embodiments, each of branch relays 3310 may include electrical terminals configured to engage with an electrical connector (e.g., of a wiring harness), to engage with individual terminating connectors of a wire bundle or cable, to be soldered to, any other suitable electrical interface, or any combination thereof. For example, installer deadfront 3330, neutral bar(s) 3304, and branch circuit breakers 3320 may be added to the assembly of FIGS. 33A-34 to create the assembly of FIGS. 36A-37B. In some embodiments, installer deadfront 3330 is installed to hide branch relays 3310 from a user, prevent access to branch relays 3310 by a user, or otherwise provide a simplified interface to a user. For example, a user can interact with, replace, install, and view branch circuit breakers 3320 without having access to branch relays 3310, which are controllable by control boards 3350 and 3351, as illustrated. In a further example, neutral bars 3304 (e.g., coupled to a Neutral of a utility service drop) may secured to installer deadfront 3330 and may include screw terminals for affixing neutral wires. Branch circuit breakers 3320 may be installed, and be electrically coupled to second terminals 3311 of each branch relay 3310 to provide protected AC power. For example, each branch circuit breaker 3320 includes a terminal to which a wire may be secured (e.g., to provide AC voltage). An outer deadfront (not shown) may be installed to cover branch circuit breakers 3320, providing access only to circuit breaker toggles 3321, which a user may interact with. As illustrated in FIGS. 36A-36D, each of branch circuit breakers 3320 may engage with a busbar (e.g., busbar 3301 or busbar 3302) and a neutral bar (e.g., either of neutral bars 3304), and may include corresponding terminals (e.g., line and neutral) to which branch circuit wiring may be terminated. In some embodiments, each of branch circuit breakers 3320 may engage busbar 3301 or 3302 and include a single output terminal, and the corresponding neutral wire may terminate at a neutral bus bar (e.g., neutral bar 3304) having a screw terminal, for example. Any suitable type of branch circuit breaker 3320 may be included (e.g., a manual breaker, a controllable breaker, a cheater breaker, a di-pole breaker), having any suitable capacity or operating characteristics, in accordance with some embodiments of the present disclosure. An assembly may include backing plate 3303, busbars 3301 and 3302, a relay layer (e.g., an array of branch relays 3310 affixed to busbars 3301 or 3302), a deadfront layer (e.g., deadfront 3330), a circuit breaker layer (e.g., an array of branch circuit breakers 3320 each affixed to busbars 3301 or 3302), and a customer deadfront layer (not shown), all arranged in an electrical enclosure.

FIG. 38A shows a front view, FIG. 38B shows a side view, FIG. 38C shows a bottom view, FIG. 38D shows a perspective view, FIG. 38E shows a perspective exploded view, and FIG. 38F shows a side exploded view of illustrative assembly 3800 including relay housing 3830 with main relay 3810 installed, main breaker 3820 installed, and busbars 3801 and 3802, in accordance with some embodiments of the present disclosure. Main relay 3810 includes two first terminals coupled to two respective busbars 3801 and 3802 (e.g., L1 and L2). Main relay 3810 also includes two second terminals coupled to two respective terminals of main breaker 3820 (e.g., corresponding to L1 and L2 housed by main bus housing 3803). Main breaker 3820 is coupled to L1 and L2 from an electrical meter, for example. Main relay 3810 may also be referred to as an “islanding relay,” because it is configured to disconnect the panel and panel circuits from the AC source (e.g., a utility service drop). As illustrated, current sensors 3811 (e.g., current transformers or any other suitable current sensor) are installed on each of L1 and L2 to sense currents in the AC lines. For example, the current sensors may be coupled to control circuitry via wires such that the control circuitry may determine the current in either or both of L1 and L2 (e.g., instantaneous, averaged or otherwise derived current). The two cable portions 3899 illustrated in FIGS. 38A-38D include sensor wires corresponding to the solid core current transformers.

FIG. 39 shows a perspective view of illustrative branch relay 3900, in accordance with some embodiments of the present disclosure. Breaker tab 3920 is the secondary terminal (e.g., secondary terminal 3311 of FIGS. 33A-34 , to which a branch circuit breaker (e.g., one of branch circuit breakers 3320 of FIGS. 35A-37B) is electrically coupled. Main bus tab 3911 is the first terminal (e.g., first terminal 3312 of FIGS. 33A-34 ), which is secured to a busbar. Shunt sense pins 3950 may provide electrical terminals to which wires may be affixed (e.g., crimped, soldered, clamped, or otherwise) for measuring a voltage difference across shunt 3960 (e.g., which includes a precise, or precisely known, resistive element). Sense pin 3951 may provide electrical terminals to which a wire may be affixed (e.g., crimped, soldered, clamped, or otherwise) for measuring a voltage at the output of branch relay 3900 (e.g., just before the corresponding branch circuit breaker). For example, sense pin 3951 and shunt sense pins 3950 may be coupled to control circuitry to determine a state of branch relay 3900, an operating condition of branch relay 3900, or any other suitable information about branch relay 3900. Main bus tab 3911 is configured to be secured to a stud of a busbar or a bolt affixed to a busbar. Shunt 3960 may include any suitable material (e.g., a metal or metal alloy such as manganin, a metallic wound wire, a thin dielectric, a carbon film), having any suitable electrical properties (e.g., resistance, impedance, and temperature dependence thereof) and any suitable geometry (e.g., flat, cylindrical, wound, a thin film with electrodes) for measuring an electrical current.

FIG. 40 shows a perspective view of illustrative branch relay 3900 and circuit breaker 4020 (e.g., forming assembly 4000), in accordance with some embodiments of the present disclosure. Branch circuit breaker 4020 is secured to breaker tab 3920 (e.g., a second terminal). For example, branch circuit breaker 4020 may include a clamp mechanism that clamps breaker tab 3920, thus maintaining electrical contact between branch circuit breaker 4020 and branch relay 3900. In some embodiments, a deadfront (not shown) may physically separate branch circuit breaker 4020 from branch relay 3900, except for openings where breaker tab 3920 protrudes. Circuit breaker 4020 includes toggle 4021 for switching, resetting, or otherwise manually controlling circuit breaker 4020.

FIG. 41 shows an exploded perspective view of illustrative panel 4100 having branch circuits, in accordance with some embodiments of the present disclosure. As illustrated, no installer deadfront is included in panel 4200, although a deadfront may optionally be included. For example, main busbars 4101 and 4102 may include respective current shunt in the branch extensions (e.g., the structures extending inward to which branch relays 4110 are secured). In a further example, main busbars 4101 and 4102 may include a comb-like structure as illustrated in FIG. 41 , and each extension configured to secure one of branch relays 4110, which may include a current shunt with sense pins or terminals to determine a branch current based on voltage drop across the shunt. In some embodiments, each of branch relays 4110 may include electrical terminals configured to engage with an electrical connector (e.g., of a wiring harness), to engage with individual terminating connectors of a wire bundle or cable, to be soldered to, any other suitable electrical interface, or any combination thereof. Branch circuit breakers 4120 may be installed, and be electrically coupled to second terminals of each branch relay 4110 to provide protected AC power. For example, each branch circuit breaker 4120 includes a terminal to which a wire may be secured (e.g., to provide AC voltage). An outer deadfront (not shown) may be installed to cover branch circuit breakers 4120, providing access only to circuit breaker toggles 4121, which a user may interact with. In some embodiments, each of branch circuit breakers 4120 may engage busbar 4101 or 4102 and include a single output terminal, and the corresponding neutral wire may terminate at a neutral bus bar having a screw terminal, for example. Any suitable type of branch circuit breaker 4120 may be included (e.g., a manual breaker, a controllable breaker, a cheater breaker, a di-pole breaker), having any suitable capacity or operating characteristics, in accordance with some embodiments of the present disclosure. An assembly may include backing plate 4103, busbars 4101 and 4102, a relay layer (e.g., an array of branch relays 4110 affixed to busbars 4101 or 4102), a deadfront layer (e.g., not shown), a circuit breaker layer (e.g., an array of branch circuit breakers 4120 each affixed to busbars 4101 or 4102), and a customer deadfront layer (not shown), all arranged in an electrical enclosure. In some embodiments, as illustrated, wires 4155 may be configured to transmit sensor signals (e.g., voltage signals) from a current shunt integrated into each relay 4110 to connectors 4156 of control boards 4150 and 4151 (e.g., which may determine current based on the voltage drop across the shunt). In some embodiments, as illustrated, wires 4155 may be configured to transmit relay control signals from control boards 4150 and 4151 to suitable terminals of branch relays 4110.

FIG. 42 shows a perspective view of illustrative installed panel 4200 having branch circuits 4220, a main breaker 4208, and autotransformer 4290, in accordance with some embodiments of the present disclosure. Several components are not shown in FIG. 42 for clarity including, for example, a customer deadfront, a panel front, incoming conduit and AC lines, and outgoing branch circuit conduits and corresponding wires. In some embodiments, electrical panel 4200 is configured to be installed in a residential structure (e.g., between sixteen-inch-spaced wall two-by-fours 4280). As illustrated, main lines L1 and L2, and the neutral line are introduced through the top of panel 4200 (e.g., in conduit coupled to a knockout in the panel top), from an electrical meter. The main lines are then routed to main breaker 4208, to the main relays (not shown), to the main busbars, to the branch relays having shunts, to the branch circuit breakers, and finally to the branch circuits (e.g., the residential wiring and outlets and ultimately electrical loads). As illustrated, autotransformer 4270 is included, and coupled to an external device (not shown). The external device may include an inverter (e.g., from a solar PV installation) or other non-grid AC source. In some embodiments, the autotransformer has a fixed winding ratio (e.g., a fixed voltage ratio). In some embodiments, autotransformer 4270 has a variable and controllable winding ratio (e.g., a variable voltage ratio). For example, autotransformer 4270 may be coupled to the main busbars and neural line via relays. When grid-connected, autotransformer 4270 may be disconnected from the busbars and neutral. When islanding, main relays and/or breaker 4208 may be opened, and autotransformer 4270 relays are closed, thus electrically coupling the branch circuit neutrals to an inverter neutral, and coupling the main busbars to lines of the inverter with suitable voltage conversion at the autotransformer.

Computer 4240 illustrated in FIG. 42 includes control circuitry configured to manage and control aspects of the electrical panel. For example, computer 4240 may be configured to control the throw position of one or more main relays (e.g., coupled to main breaker 4208), one or more branch relays, any other suitable relay or controllable switch, or any combination thereof (e.g., of branch circuits 4220). In a further example, computer 4240 may be configured to receive analog signals from a sense pin (e.g., to determine a state of a relay), shunt sense pin (e.g., to determine a current), a current sensor (e.g., to determine a current), a voltage sensor (e.g., to determine a voltage), a temperature sensor (e.g., to determine a surface, component, or environmental temperature), any other suitable signal, or any combination thereof. Computer 4240 may include a power supply, a power converter (e.g., a DC-DC, AC-AC, DC-AC, or AC-DC converter), a digital I/O interface (e.g., connectors, pins, headers, or cable pigtails), an analog-to-digital converter, a signal conditioner (e.g., an amplifier, a filter, a modulation), a network controller, a user interface (e.g., a display device, a touchscreen, a keypad), memory (e.g., solid state memory, a hard drive, or other memory), a processor configured to execute programmed computer instructions, any other suitable equipment, or any combination thereof. In some embodiments, panel 4200 of FIG. 42 includes one or more control boards coupled to branch relays, main relays, and the computer. In some embodiments, computer 4240 is coupled directly to branch relays, main relays, sensors, any other suitable components of the panel, or any combination thereof.

In an illustrative example, in the context of FIGS. 31-42 , an electrical panel may allow branch circuit monitoring. In some embodiments, high-accuracy branch circuit monitoring may be achieved, because each circuit is populated with an integrated shunt (e.g., with a calibrated resistive element) configured to measure the current flowing through each circuit. Electrical power in each branch circuit may be determined based on the current and voltage. For each branch circuit, this functionality provides the ability to perform in-line measurement of real power, reactive power, energy, any other suitable parameters, or any combination thereof. In some embodiments, for the mains (e.g., L1 and L2) entering the panel, high-accuracy solid-core current sensors (e.g., current shunts) are assembled on each busbar to provide energy metering on each branch circuit (e.g., whole-home metering). In some embodiments, the control boards are designed to accommodate pre-assembled shunts, split-core CT inputs (e.g., to measure retrofitted PV circuits, sub-panel, or other similar devices connected to the panel), or both.

In an illustrative example, in the context of FIGS. 31-42 , an electrical panel may allow branch circuit control. In some embodiments, each branch circuit is fitted with a controllable relay that is directly mounted on a main busbar thus allowing for individual circuit level controls. In some embodiments, the branch relay's inputs allow for easy installation within an electrical panel and the breaker tabs are designed to accommodate standard molded-case circuit breakers. In some embodiments, each relay is actuated independently and in real-time by control circuitry, thus allowing for software-defined load controls within the panel. In some embodiments, relays are designed such that the only exposed component of the panel to the installer is the breaker tab where the branch circuit breaker is mounted (e.g., the installer deadfront hides the remaining portion of the relay). In some embodiments, the branch relay breaker tab is provided with a sense pin configured to detect the throw position of the relay in real-time (e.g., on or off based on the voltage at the sense pin). A relay may have any suitable rating, capacity, or operating characteristics, in accordance with some embodiments of the present disclosure. In an illustrative example, a branch relay may be rated to 90A (e.g., higher than a typical residential circuit or circuit breaker), which allows for the branch circuit breaker to operate normally as the passive safety device.

In an illustrative example, in the context of FIGS. 31-42 , an electrical panel may have an architecture that allows branch level sensing and actuation. In some embodiments, the branch level sensing and actuation is achieved using a control board. In some embodiments, the control board is configured to receive analog signals from a plurality of shunt resistors. In some embodiments, the control board may include relay drivers configured to receive control signals from control circuitry (e.g., low-voltage DC signals generated by a gateway computer). A control board may include an analog-to-digital converter, a digital I/O interface, a power supply or power conversion module, any other suitable components or functionality, or any combination thereof. In some embodiments, an electrical panel includes two control boards, arranged one on either side of the interior of the panel and each with the ability to manage a plurality of circuits (e.g., simultaneously). For example, a panel may include twenty circuit branches on each side of the panel. In some embodiments, a busbar configuration allows for inter-changing lines L1 and L2 connections, making it possible to connect a di-pole breaker (e.g., for a 240 VAC branch coupled to both L1 and L2). In some embodiments, one or more control boards and associated control logic allow for configuring current sensors and relay actuators in groups or clusters. For example, a relatively large load connected to a di-pole breaker could be configured to be treated as a single branch for the purposes of energy metering and load controls. In some embodiments, control boards are connected to a main board (e.g., a carrier board) that is capable of performing additional computations as well as supporting software applications.

In an illustrative example, in the context of FIGS. 31-42 , an electrical panel may include one or more autotransformer (e.g., a single winding transformer). Many solar/hybrid inverters require an external autotransformer to provide a neutral reference for phase-balanced loads. In some embodiments, an electrical panel includes an autotransformer that is enabled/sourced (e.g., through a pair of relays) during off-grid operations (e.g., when islanding). In some embodiments, the control circuitry may include control logic that ensures that the autotransformer is only connected to one or more busbars during off-grid operations. In some embodiments, an electrical panel is designed to provide suitable cooling for an autotransformer. For example, cooling may be achieved by passive or active cooling elements such as fins, fans, heat exchangers, any other suitable components, or any combination thereof. An autotransformer may include a fixed primary-secondary voltage ratio, or may include a variable primary-secondary voltage ratio. In an illustrative example, a solar PV inverter may provide a first AC voltage, which may be reduced by the autotransformer to match the line-neutral voltage between a busbar and the neutral of the panel. Accordingly, the solar PV system need not output the same AC voltage as required by electrical loads.

In an illustrative example, in the context of FIGS. 31-42 , an electrical panel may include one or more busbars. Each busbar may be designed to easily couple to a main breaker and a main relay, as well as a plurality of branch circuit breakers through a plurality of branch relays having corresponding shunt resistors. In some embodiments, a busbar may include or having installed with threaded studs (e.g., pem studs) to allow for easy alignment and assembly with each branch relay while ensuring that the L1, L2 configuration inside a panel is preserved (e.g., to meet industry standards). In some embodiments, a busbar is designed with terminals (e.g., spring terminals or screw terminals) to allow devices such as sub-panels to be powered from the panel without the need for branch circuit breakers.

In an illustrative example, in the context of FIGS. 31-42 , an electrical panel may include one or more deadfronts. In some embodiments, the sensing and relay actuation mechanism and control boards are assembled underneath an installer deadfront to ensure that the installation process is simplified/modular. In some embodiments, a neutral bar is mounted on the installer deadfront to allow plug-on neutral breakers to both be aligned with and serve as a path of current return for each circuit. In some embodiments, the only exposed portions of the relays are the breaker tabs to which the branch circuit breakers are mounted to. In some embodiments, an electrical panel includes a customer deadfront that goes in front of the breakers and the load wiring which only exposes the breaker toggles to the customer (e.g., a panel may, but need not, include an installer deadfront and a customer deadfront). In some embodiments, a status light for each branch circuit is embedded on the customer deadfront for ease of debugging the system as well as providing visual feedback on the status of individual circuits. For example, a plurality of LEDs may be included on the deadfront, and the LEDs may be wired to control circuitry configured to turn the LEDs on and off. In a further example, LEDs may include LEDs of different colors, size, or shape configured to indicate various states of the panel or circuits coupled thereto.

The systems and methods of the present disclosure may be used to, for example, provide circuit level prediction for load forecasting, managed backup controls and energy optimization using main circuit, branch circuit and/or appliance controls, dynamic time-remaining estimates incorporating circuit-level load and forecasting (e.g., solar forecasting), software-configured backup with real-time feedback, hardware safety for phase imbalance or excessive phase voltage in a panelboard serving an islanded electrical system, a plurality of metering circuits connected to common circuitry, monitoring of current transducers associated with one busbar, firmware updates of an electrical panel, a connection to distributed energy resources, a connection to appliances, third-party application support for distributed energy and home automation, grid health monitoring, energy reserve, and power flow management, any other suitable functionality, or any combination thereof.

The consumption of a home is predicted using high-frequency, short-term load forecasting on a circuit level, an appliance level, or both. High frequency measurements on the circuit level may be disaggregated to identify individual appliances using, for example, a non-intrusive (e.g., appliance level) load monitoring algorithm. Information on circuit usage, appliance usage, consumption, or a combination thereof are extracted from the data and used to group the circuits and/or appliances into different categories using a clustering/classification algorithm to identify similar usage and consumption pattern. Depending on the category, a different forecast model is applied to account for specific consumption characteristics. The circuit/appliance level load predictions are aggregated to the household level.

In an illustrative example, measurements of current for each circuit branch and bus voltages may be used to determine electrical load at a given time, or over time, in a circuit. Information such as which appliances are connected to each branch, the temporal or spectral character of the current draw for those appliances, historical and/or current use information (e.g., time of day, frequency of use, duration of use), or any other suitable information may be used to disaggregate branch level measurements.

FIG. 43 shows illustrative system 4300 for managing electrical loads and sources, in accordance with some embodiments of the present disclosure. System 4300 includes control system 4310, AC bus 4320, one or more branch circuits 4330, one or more appliances 4340, one or more devices 4380 (e.g., which may include loads and/or sources), user device 4350, and network device 4360. Sensors may be coupled to control system 4310, AC bus 4320, one or more branch circuits 4330, one or more appliances 4340, one or more devices 4380, or a combination thereof, and provide sensor signals to sensor system 4313. Control system 4310, as illustrated, includes control circuitry 4311, memory 4312, sensors system 4313 (e.g., which may include any component described herein for measuring current, voltage, or other electrical signals, and any suitable sensor interface), communications interface 4314. Also, as illustrated, control system 4310 is coupled to AC bus 4320 (e.g., for voltage measurement, and main disconnect control), one or more branch circuits 4330 (e.g., for current measurement, breaker/relay control, or both), one or more appliances 4340 (e.g., to determine an appliance identifier (ID), directly control appliance operation, retrieve applicant information), or a combination thereof. To illustrate, system 4300 may be implemented using an integrated electrical panel (e.g., that includes control system 4310, AC bus 4320, and portions of branch circuits 4330), a distributed EMS system (e.g., a plurality of systems similar to control system 4310 may be linked communicatively), any other suitable configuration, or any combination thereof.

User device 4350, illustrated as smartphone, is coupled to communications network 4301 (e.g., connected to the Internet). User device 4350 may be communicatively coupled to communications network 4301 via USB cables, IEEE 1394 cables, a wireless interface (e.g., Bluetooth, infrared, WiFi), any other suitable coupling or any combination thereof. In some embodiments, user device 4350 is configured to communicate directly with control system 4310, one or more appliances 4340, network device 4360, any other suitable device, or any combination thereof using near field communication, Bluetooth, direct WiFi, a wired connection (e.g., USB cables, ethernet cables, multi-conductor cables having suitable connectors), any other suitable communications path not requiring communication network 4301, or any combination thereof. User device 4350 may implement energy application 4351, which may send and receive information from communication interface 4314 of control system 4310. Energy application 4351 may be configured to store information and data, display information and data, receive information and data, analyze information and data, provide a visualization of information and data, otherwise interact with information and data, or a combination thereof. For example, energy application 4351 may interact with usage information (e.g., electrical load over time, electrical load per branch circuit), schedule information (e.g., peak usage, time histories, duration histories, planned operation schedules, predetermined interruptions), reference information (e.g., a reference usage schedule, a desired usage schedule or limit, thresholds for comparing operation parameters such as current or duration), historical information (e.g., past usage information, past fault information, past settings or selections, information from a plurality of users, statistical information corresponding to one or more users), energy information (e.g., energy source identification, power supply characteristics), user information (e.g., user demographic information, user profile information, user preferences, user settings, user generated settings for responding to faults), any other suitable information, or any combination thereof. In some embodiments, energy application 4351 is implemented on user device 4350, network device 4360, or both. For example, energy application 4351 may be implemented as software or a set of executable instructions, which may be stored in memory storage of the user device 4350, network device 4360, or both and executed by control circuitry of the respective devices.

Network device 4360 may include a database (e.g., including usage information, schedule information, reference information, historical information, energy information, user information), one or more applications (e.g., as an application server, host server), or a combination thereof. In some embodiments, network device 4360, and any other suitable network-connected device, may provide information to control system 4310, receive information from control system 4310, provide information to user device 4350, receive information from user device 4350, provide information to one or more appliances 4340, receive information from appliances 4340, or any combination thereof.

Device(s) 4380 may include, for example, a battery system, an electric vehicle charging station (e.g., an EV charger configured to be electrically coupled to an EV), a solar panel system, a DC-DC converter, an AC-DC converter, and AC-AC converter, a transformer, any other suitable device coupled to an AC bus or DC bus, or any combination thereof. For example, device(s) 4380 may be configured to communicate directly with, or via communications network 4301 with, any of control system 4310, user device 4350, one or more appliances 4340, and network device 4360.

In an illustrative example, system 4300, or control system 4310 thereof, may be configured to implement any of the illustrative use cases of table 2300 of FIG. 23 . In a further example, system 4300, or control system 4310 thereof, may be configured to implement IoT arrangement 2400 of FIG. 24 . In a further example, system 4300, or control system 4310 thereof, may be configured to implement process 2500 of FIG. 25 .

In an illustrative example, control system 4310 may use labels or identifiers provided by the installer, retrieved from a device, or otherwise received to provide backing context to a disaggregation algorithm (e.g., energy application 4351). Because the branch circuits are individually monitored and controlled, the load in each circuit may be classified, modeled, or otherwise characterized based on the intended use (e.g., kitchen appliances, lighting, heating), thus reducing the algorithmic complexity required for control system 4310 to associate measured electrical characteristics with reference load types. To illustrate, control system 4310 may receive at least one sensor signal from sensor system 4313 configured to measure one or more electrical parameters corresponding to one or more branch circuits 4330. Control system 4310 associates one or more of branch circuits 4330 with reference load information (e.g., stored in memory 4312), which can include expected load (e.g., peak load, maximum load, power factor, startup transients, duration or other temporal characteristics), expected power consumption, power capacity information (e.g., expected power capacity), any other suitable information, or any combination thereof. Based on the sensor signal received at, or generated by, sensor system 4313, control system 4310 (e.g., control circuitry 4311 thereof) determines a respective electrical load in the one or more branch circuits based on the sensor signal. Control system 4310 (e.g., control circuitry 4311 thereof) disaggregates more than one load on a branch circuit based at least in part on the reference load information and based at least in part on the respective electrical load in the one or more branch circuits. Control system 4310 (e.g., control circuitry 4311 thereof) controls a respective controllable element (e.g., a controllable breaker or relay) to manage the respective electrical load in each respective branch circuit. To illustrate, control system 4310 (e.g., control circuitry 4311 thereof) identifies which components are loading a particular branch circuit (e.g., based on an expected power or current profile). To illustrate further, control system 4310 (e.g., control circuitry 4311 thereof) forecasts power or current behavior of a particular branch circuit based on the loads coupled to the branch circuitry (e.g., for which reference load information if available). In some embodiments, control system 4310 (e.g., control circuitry 4311 thereof) identifies an event associated with a power grid coupled to one or more branch circuits 4330 (e.g., via AC bus 4320), determines operating criteria based on the event, and disconnects or connects branch circuits of one or more branch circuits 4330 based on the operating criteria. As an illustrative example, control system 4310 may use disaggregated load identifications to anticipate inverter overload before an overload occurs by projecting out power demand for each active appliance in a household based on those appliances' cyclic power characteristics, historical usage information of the appliances, and disconnect circuits in order to prevent said overload.

In some embodiments, a first step includes control circuitry 4311 causing user-defined circuits (e.g., one or more of branch circuits 4330) to be automatically disconnected in different stages to reduce power consumption. In some embodiments, a first set of loads (e.g., less critical loads, or highly draining loads) are disconnected as soon as the system goes off-grid (e.g., AC bus 4320 is disconnected from a power grid). Accordingly, the other stages are then connected or disconnected as soon as pre-defined battery state of charge levels are reached (e.g., by a battery system of devices 4380 coupled to AC bus 4320 via an AC-DC converter of devices 4380). The state of each branch or main circuit can optionally be changed by a user (e.g., by interacting with communications interface 4314) or control system 4310 in real-time. In some embodiments, control system 4310 monitors and/or manages phase imbalance (e.g., among two phases loaded equally exceeding an inverter's output capability, or on a single phase) to extend uptime (e.g., during backup an energy optimization is used in the second step), avoid inverter overload, preserve power to systems deemed critical, or a combination thereof. In some embodiments, optimal or otherwise determined load shifting and/or curtailment measures for one or more appliances 4340 are identified based on, for example, load forecast, solar power prediction, user preferences, appliance information, or a combination thereof. In some embodiments, control system 4310 communicates (directly or indirectly) with individual devices (e.g., one or more appliances 4340, devices 4380) to adjust the power level and operating time (e.g., in the event of a grid blackout or other power disruption).

FIG. 44 shows illustrative graphical user interface (GUI) 4400, including an indication of system characteristics, in accordance with some embodiments of the present disclosure. In an illustrative example, GUI 4400 may be generated by a user device (e.g., user device 4350 of FIG. 43 ), implementing an application (e.g., energy application 4351 of FIG. 43 ), on a screen of the user device (e.g., or another suitable device). To illustrate, GUI 4400 may be displayed on a touch screen of a smartphone, a screen included in an interface of control system 4310, any other suitable device, or any combination thereof. As illustrated, GUI 4400 includes user device status information 4401, which may include, for example, time, date, communications signal strength, network communications strength, user device battery life, user device notifications, warnings, any other status information, or any combination thereof. As illustrated, GUI 4400 includes time estimates 4402, which may include, for example, an estimated time duration of power supply, an estimated operating life of a load or source, an estimated remaining time, a graphic illustrating power allocation, a graphic illustrating operating life for classes of loads (e.g., “must have,” “nice to have,” and “nonessential”), an amount of energy allotted or remaining for a load, any other information indicative of use of a finite power source (e.g., a battery pack during a grid disconnect), or any combination thereof. As illustrated, GUI 4400 includes circuit classifier 4403, which may include, for example, a classification of loads or branch circuits, selectable options for classifying loads or branch circuits, descriptions of each classification (e.g., “must have,” “nice to have,” and “nonessential” as illustrated), load preferences (e.g., which loads to turn off first, an order or ranking, or which loads are prioritized), any other information indicative of classification or options related to classification, or any combination thereof. For example, a user may drag the icons for each circuit (e.g., “pool” or “basement”, etc.) to any classification to modify the electric power allotment and scheduling. As illustrated, GUI 4400 includes options 4404, which may include, for example, dashboard (e.g., the screen illustrated in FIG. 44 ), control options (e.g., for adjusting energy scheduling, user profile information, device information, communication information, time durations, instructions for managing energy loads, specifying load preferences, or a combination thereof), scheduling options (e.g., for scheduling disconnection and connection of branch circuits, maintenance, disconnection from grid, updating of software, storage of data), limits (e.g., on any suitable operating parameters), any other options for interacting with GUI 4400, or any combination thereof.

In some embodiments, control system 4310 (e.g., control circuitry 4311 thereof) executes an algorithm that generates real-time estimates of remaining time in backup for residences having a backup battery system, illustrated via GUI 4400 of FIG. 44 (e.g., generated by an interface of control system 4310 or a user's mobile device). In some embodiment, the algorithm takes into account instantaneous power draw from individual circuits in the house (e.g., each branch circuit), load forecasting based on historical data from those same circuits (e.g., or from other users based on statistical analysis), solar forecasting based on historical data, weather forecasts (e.g., provided by third parties), any other suitable information or forecast based on information, or any combination thereof. For example, as user behavior patterns change or loads are switched on/off by control system 4310, the estimates and settings illustrated in GUI 4400 of FIG. 44 may change in real time.

In some embodiments, control system 4310 includes real-time switching and metering capability for each circuit in a house, as well as the ability to island the house from the grid during grid outages. For example, control system 4310 provides the ability to configure which circuits will be powered while off-grid through a user interface (e.g., energy application 4351 of FIG. 43 , GUI 4400 of FIG. 44 ). The system allows this configuration to be achieved in real-time. While the user is configuring which loads will be powered while off-grid, the system utilizes historical measurements from those circuits to provide real-time feedback to the user, including but not limited to, warning of potential overload when too many circuits are configured to be powered; warning of potential phase imbalance; and providing feedback as to the estimated time that the system will be able to power the selected loads. In some embodiments, control system 4310 (control circuitry 4311 thereof) automatically sheds load(s) to prevent overload, ensure continuity of power overnight or through cloudy days, or both. In some embodiments, the operating criteria may include partition of loads indicating which can be shed or in what order loads are shed (e.g., “nice to haves” are shed before “must haves”).

In addition, in some embodiments, control system 4310 uses clustering and/or categorization algorithms to identify those loads which are operated in distinct cycles consuming regular amounts of energy, such as dishwashers or electric dryers. In some embodiments, control system 4310 determines average energy usage for each cycle and detects the start of cycles. When a cycle begins while the house is off-grid, for example, control system 4310 notifies the homeowner of the expected change in battery energy level. In some embodiments, control system 4310 notifies the homeowner (e.g., at the user interface) when the battery energy level falls below the amount necessary to run a complete cycle of any of the loads in the house. If In some embodiments, control system 4310 detects the start of a cycle in this condition, it issues a warning to the homeowner that the cycle may not complete.

In some embodiments, system 4300 or other integrated system includes a circuit breaker panelboard designed for connection to both a utility grid as well as a battery inverter (e.g., of devices 4380) or other distributed energy resource, and containing one or more switching devices on the circuit connecting the panelboard to the utility point of connection, as well as switching devices on branch circuits 4330 serving loads. In some embodiments, system 4300 includes voltage measurement means (e.g., voltage sensors coupled to sensor system 4313) connected to all phases of the utility grid side of the utility point of connection circuit switching device, which are connected to logic circuitry (e.g., control circuitry 4311 of control system 4310) capable of determining the status of the utility grid. Furthermore, In some embodiments, control system 4310 may include logic devices capable of generating a signal to cause the switching device to disconnect the panelboard from the utility grid when the utility grid status is unsuitable for powering the loads connected to the panelboard, thereby forming a local electrical system island and either passively allowing or causing (through electrical signaling or actuation of circuit connected switching devices) the distributed energy resource to supply power to this island. In some embodiments, In some embodiments, control system 4310 determines a preprogrammed selection of branch circuits which are to be disabled when operating the local electrical system as an island, in order to optimize energy consumption or maintain the islanded electrical system power consumption at a low enough level to be supplied by the distributed energy resource. In some embodiments, In some embodiments, control system 4310 includes logic that uses forecasts of branch circuit loads, or of appliance loads, or measurements of branch circuit loads, to dynamically disconnect or reconnect branch circuits to the distributed energy resource, or send electrical signals to appliances on branch circuits enabling or disabling them, in order to optimize energy consumption, or maintain the islanded electrical system power consumption at a low enough level to be supplied by the distributed energy resource. In some embodiments, In some embodiments, control system 4310 includes an energy reservoir device, such as one or more capacitors, capable of maintaining logic power and switching device actuation power in the period after the utility grid point of connection circuit switching device has disconnected the electrical system from the utility grid, and before the distributed energy resource begins to supply power to the islanded electrical system, in order to facilitate actuation of point of connection and branch circuit switching devices to effect the aforementioned functions.

In some embodiments, system 4300 or other integrated system includes a circuit breaker panelboard designed for connection to a battery inverter or other distributed energy resource and operating in islanded mode, with the served AC electrical system (e.g., via AC bus 4320) disconnected from any utility grid; the distributed energy resource supplying power to the panelboard being connected to it via a connection incorporating fewer power conductors (hereafter “conductors”) than the electrical system served by the panelboard, and said panelboard incorporating or designed for connection to a transformer or autotransformer provided with at least one set of windings with terminals equal in number to the number of conductors of the electrical system served by the panelboard, with said transformer being designed to receive power from a connection incorporating the same number of power conductors as the connection to the distributed energy resource.

In some embodiments, the panelboard incorporates a plurality of electronic hardware safety features and additionally a plurality of electrical switching devices, with said safety features designed to monitor either the difference in voltage of all of the power conductors of the supplied electrical system, or designed to monitor the difference in voltage of each of the conductors of the electrical system with respect to a shared return power conductor (“neutral”), said voltages hereafter termed “phase voltages”, or a suitable combination of monitoring of difference in voltages and phase voltages such that the power supply voltage to all devices served by the electrical system is thereby monitored.

In some embodiments, the plurality of safety features are designed to retain safe behavior when subject to a single point component or wiring fault, and intended to entirely disconnect the connection between the distributed energy resource and the panelboard if conditions that could lead to excessive voltages being supplied to any load served by the panelboard are detected.

For example, a panelboard connected to a 240V battery inverter that is provided with two terminals by two conductors, said panelboard incorporating an autotransformer provided with two windings and three terminals, and said panelboard serving an islanded electrical system of the 120V/240V split phase type, where three conductors are used to supply two 120V circuits with respect to a shared neutral return conductor, each of said 120V conductors being supplied with power 180 degrees out of phase with respect to the other, and with said panelboard containing a complement of said safety features, wherein the safety features include:

1. A single phase 240V battery inverter containing an overvoltage detection circuit, which disables output of the inverter when excessive voltages are detected.

2. A central voltage imbalance detector circuit, which sends a signal when an imbalance in phase voltage is detected.

3. Two separate actuation circuits associated with two separate switching devices, each switching device being in circuit with the battery inverter.

4. Two voltage amplitude detector circuits, one associated with each switching device, and each monitoring one phase of the electrical system.

5. Actuation circuits being designed to disconnect the associated switching device if either the central voltage imbalance detector signal is transmitted, or an excessive voltage associated with the monitored electrical system phase is detected, or if the logic power supply to the actuation circuit is lost.

6. Optionally, an energy reservoir associated with each actuation circuit, to enable each actuation circuit to take the action needed to disconnect the switching device after loss of logic power supply to the actuation circuit, especially if the switching device is bi-stable.

In some embodiments, system 4300 uses an energy reservoir and dual-redundant circuitry to cause latching relays to fail-safe open, thus reducing energy consumption (e.g., and heat generation) in components of system 4300 while maintaining single-fault tolerance.

In some embodiments, system 4300 or another integrated system includes an electrical panelboard containing at least one power distribution conductor (“busbar”, the term being a placeholder and here incorporating all manner of rigid or flexible power distribution conductors) that distributes power to multiple branch circuits, each branch circuit incorporating current transducers such as current measurement shunts, or non-isolated current transformers, or non-isolated Rogowski coils. Wherein all branch circuits (e.g., one or more branch circuits 4330) associated with a given bus bar (e.g., of AC bus 4320) are monitored by a plurality of metering circuits that each measure current or power associated with a given branch circuit or set of branch circuits, said metering circuits being connected together without need for galvanic isolation, and said metering circuits being provided with or incorporating a system of common mode filters, or differential amplifiers, or both, such that the metering circuits are able to produce accurate results from the signals generated by the current transducers even in the presence of transient or steady state voltage differences existing between the transducers of each branch circuit served by the bus bar, which result from voltage differences associated with current flow through the resistive or inductive impedance of the bus bar and branch circuit system, and are coupled to the current transducers either by direct galvanic connection or capacitive coupling, parasitic or intentional.

As described herein, non-isolated is understood to mean the condition which exists between two electrical conductors either when they are in direct electrical contact, or when any insulation or spacing between them is of insufficient strength or size to provide for the functional or safety design requirements which would be needed if one of the conductors were energized by a potential associated with a conductor in the electrical system served by the panelboard, and the other conductor were to be either left floating, or connected to a different potential served by the electrical system.

In some embodiments, system 4300 includes metering circuits that share a common logic or low voltage power supply system.

In some embodiments, system 4300 includes a power supply system that is galvanically bonded to the busbar (e.g., of AC bus 4320) at one or more points.

In some embodiments, system 4300 includes metering circuits sharing a non-isolated communication medium.

In some embodiments, system 4300 includes metering circuits that are collocated on a single printed circuit board, which is physically close to the busbar (e.g., of AC bus 4320) and is sized similarly in length to the bus bar, and in which a printed low voltage power distribution conductor associated with the metering circuits is electrically connected to the bus bar at a single central point, near the middle of the length of the busbar.

In some embodiments, electrical connection to the busbar (e.g., of AC bus 4320) is made by means of a pair of resistances connected between the printed power distribution conductor and each of the leads associated with a single current measurement shunt type of current transducer, which serves one of the branch circuits, said transducer being located close to the middle of the length of the busbar, and with said resistances being sized such that any current flow caused through them by the potential drop across the shunt transducer is negligible in comparison to the resistance of the shunt and the resistances of any connecting conductors that connect the shunt to the resistances, so as not to materially affect the signal voltage produced by the transducer when said current flows.

In some embodiments, a pair of systems are used (e.g., two control systems 4310 and two sets of loads and sources), one associated with each line voltage bus bar of a split phase 120V/240V electrical panelboard. For example, each of the systems is connected to a central communication device or computing device by means of a galvanically isolated communications link, and in which each system is served by a separate, galvanically isolated power supply.

In some embodiments, an Internet-connected gateway computer serves as a home energy controller and also distributes over-the-air firmware updates to connected devices throughout the house. The computer is capable of receiving over-the-air firmware updates through wired and wireless Internet connections. A genericized firmware update process allows firmware packages for connected distributed-energy resources, including but not limited to solar inverters, hybrid inverters, and batteries, as well as home appliances to be included in the firmware update package for the gateway, such that the gateway can then update those devices and appliances. To illustrate, control system 4310 may distribute over-the-air communications (OTAs) through powerline communication, wireless communication, Ethernet networks, serial buses, any other suitable communications link, or any combination thereof.

In some embodiments, an Internet-connected gateway computer, serving as an energy management system (EMS) for a residence, runs programs (“apps”) compiled for the computer by third parties intended to contribute to the management of the distributed energy resources in the residence, and provides those programs with measurements and control capabilities over those distributed energy resources. Information is exchanged between programs through a secure internal API.

FIG. 45 shows a diagram of system 4520 (e.g., a PCS) having elements for multiple-redundant control and monitoring, in accordance with some embodiments of the present disclosure. Arrangement 4500 includes system 4520 (e.g., an integrated panel, having programmable controller 4525), point of interconnection (POI) 4510 (e.g., connecting to an AC grid), directly controllable loads and sources 4530, loads and sources 4540 without direct communication to programmable controller 4525, and sources 4550 (e.g., DERs). To illustrate, in some embodiments, additional layers of monitoring and control may be expanded by establishing communication to capable loads and generation sources (DERs).

In some embodiments, for example, POI 4510 corresponds to main utility service input 110 of FIG. 1 . POI 4510 is coupled to primary overcurrent protection device (OCPD) 4521, which may include a main service breaker (e.g., similar to main service breaker 112 of FIG. 1 ), and optionally a controllable main relay. Overcurrent protection devices (OCPD) 4522 (e.g., circuit breakers) and actuators 4523 (e.g., relays) may correspond to a plurality of branch circuits (e.g., any of respective branch circuits 156 of FIG. 1 or branch circuit(s) 4330 of FIG. 43 ). To illustrate, each OCPD of OCPDs 4522 may correspond to a branch circuit and may be coupled to an AC line (e.g., “L1” or “L2” busbar of a 240 VAC system, or any other suitable line). To illustrate further, each actuator of actuators 4523 may correspond to a branch circuit and may be coupled to an AC line (e.g., “L1” or “L2” busbar of a 240 VAC system, or any other suitable line). It will be understood that OCPDs 4522 and actuators 4523, for each branch, may be arranged in any suitable order (e.g., either may interface directly to a busbar, and the other may interface to load wires).

Power monitor 4524 is configured to sense bus current (e.g., of L1 and L2) and branch current and, as illustrated, is coupled to each of actuators 4523 (e.g., relays having or coupled to current sensing shunts as illustrated in FIGS. 32-37B and 39-41 ). Programmable controller 4525 is configured to receive input from power monitor 4524, provide control signals to actuators 4523, communicate with loads and sources 4530 (e.g., EVSE such as an EV charger, smart appliances, or other suitable devices), communicate with sources 4550, manage electric power production and consumption, any other suitable functions, or any combination thereof. To illustrate, for example, control circuitry may include power monitor 4524 and programmable controller 4525, and may be similar to, the same as, or included as part of onboard computer 118 of FIG. 1 , gateway 503 of FIGS. 6-16 , control circuitry 3130 of FIG. 32 , or control circuitry 4311 of FIG. 43 . In some embodiments, programmable controller 4525 may execute computer-readable instructions for managing loads, sources, operation of system 4520, communication with devices, or any combination thereof.

System 4520 is electrically coupled to loads, sources, or both (e.g., via branch circuits and wiring, transformers, AC-DC converters, or a combination thereof). Each of loads and sources 4530, loads and sources 4540, and sources 4550 may be coupled to branch circuits of system 4520 (e.g., each corresponding to an OCPD and actuator of system 4520). To illustrate, loads and sources 4530, loads and sources 4540, and sources 4550 may include suitable components of appliance(s) 4340 and device(s) 4380 of FIG. 43 .

FIG. 46 is a flowchart of illustrative process 4600 for controlling electrical loads, in accordance with some embodiments of the present disclosure. In some embodiments, process 4600 includes illustrative application logic followed by a multilevel control scheme, in accordance with some embodiments of the present disclosure. In some embodiments, each of step of process 4600 is implemented as a fallback to the previous step. For example, by combining communications-enabled generation sources and loads with a fallback layer of series actuators capable of interrupting current to loads, the system can offer functionally safe current limiting with reduced user experience impact as compared to an actuator-only approach. In an illustrative example, process 4600 may be an example of process 2500 of FIG. 25 , wherein the system processes information based on inputs, and controls one or more devices to maintain energy consumption within a limit. In a further example, process 4600 may be implemented by onboard computer 118 of FIG. 1 , gateway 503 of FIGS. 6-16 , control system 4310 of FIG. 43 , system 4520 of FIG. 45 , or any other suitable system or device of the present disclosure.

Step 4602 includes the system determining whether energy consumption is near, at, or greater than a limit. At step 4602, the system determines an energy consumption such as, for example, a total power (e.g., voltage multiplied by current), a sum of branch circuit power (e.g., sum of voltage multiplied by branch current), a sum of device power consumptions (e.g., as modeled or otherwise determined based on branch loads), an output of a model, a smoothed or filtered energy consumption (e.g., a time average or ensemble average), an input received from another system or device, any other suitable value indicative of energy consumption, or any combination thereof. In some embodiments, at step 4602, the system determines the limit based on reference information (e.g., a predetermined limit stored in memory), user input (e.g., as received at a user input interface), information received from another system or device, sensor signals (e.g., temperature signals, current signals, or any other suitable signals), a scheduled limit (e.g., a predetermined calendar of limit values per minute, hour, or day), an amount of energy production or transfer (e.g., from one or more energy sources), any other suitable information, or any combination thereof. In some embodiments, at step 4602, the system compares the energy consumption (e.g., a numerical value, collection of values, or other suitable designation such as a level or range) to the limit (e.g., a numerical value, designation, or a range), and based on the comparison, the system determines whether to modify loads, sources, or both. In some embodiments, at step 4602, the system determines whether the energy consumption is within a predetermined numerical proximity of the limit (e.g., based on a difference between the energy consumption and the limit). In some embodiments, at step 4602, the system determines whether the energy consumption is equal to or greater than the limit (e.g., based on a difference, ratio, or other suitable comparison). The system may compare the energy consumption and the limit based on instantaneous values (e.g., a current energy consumption value), values over time (e.g., an averaged or otherwise filtered difference), a model (e.g., having inputs and outputs), derived values (e.g., derivatives, integrals, transforms), any other suitable information or values, or any combination thereof.

Step 4604 includes the system generating one or more control signals, corresponding to one or more energy sources, to affect electrical energy production. In an illustrative example, the one or more energy sources may include any of device(s) 4380 of FIG. 4380 such as, for example, a battery system, an electric vehicle charging station, a solar panel photovoltaic system, a DC-DC converter, an AC-DC converter, and AC-AC converter, a transformer, a generator, any other suitable device coupled to an AC bus or DC bus, or any combination thereof. Each control signal may include an analog signal, a digital signal (e.g., in serial or parallel, or a combination thereof), a message (e.g., transmitted using any suitable protocol), a relay/switch signal (e.g., on/off, or one position of a multi-position switch), a waveform (e.g., having a frequency, phase, amplitude, and/or other characteristic), a pulse-based signal (e.g., a pulse-width modulated signal, a pulse-density modulated signal), any other suitable signal, or any combination thereof. In some embodiments, at step 4604, the system generates a control signal corresponding to an energy source to cause the energy source to increase power generation or transfer to lessen the chance of the energy consumption exceeding the limit. In some embodiments, the system includes a signal generator, communications bus, communications interface (e.g., communications interface 4314), or any other suitable components for generating a software signal (e.g., included in a gateway), electrical signal, optical signal, wireless signal, any other suitable signal, or any combination thereof. In some embodiments, step 4604 includes the system transmitting the one or more control signals over one or more communications links. The one or more control signals may be transmitted over a cable (e.g., a multiconductor cable), a communications bus, one or more wires, one or more fiber optics, one or more wireless signals (e.g., transmitted and received by antennas), control circuitry (e.g., of a PCB), any other suitable communications link, or any combination thereof. In an illustrative example, step 4604 may include the system sending one or more control signals to communications-enabled generation sources (e.g., solar panels, battery system) to increase or decrease production.

Step 4606 includes the system generating one or more control signals, corresponding to one or more loads, to affect electrical energy consumption. In an illustrative example, the one or more loads may include any of appliance(s) 4340 or device(s) 4380 of FIG. 4380 , as well as loads on any of branch circuit(s) 4330, such as, for example, lighting, outlets, kitchen appliances, other appliances, motors (e.g., for fans, pumps, compressors), electronics (e.g., computers, entertainment systems, sound systems), any other suitable electrical loads, or any combination thereof. Each control signal may include an analog signal, a digital signal (e.g., in serial or parallel, or a combination thereof), a message (e.g., transmitted using any suitable protocol), a relay/switch signal (e.g., on/off, or one position of a multi-position switch), a waveform (e.g., having a frequency, phase, amplitude, and/or other characteristic), a pulse-based signal (e.g., a pulse-width modulated signal, a pulse-density modulated signal), any other suitable signal, or any combination thereof. In some embodiments, at step 4606, the system generates a control signal corresponding to a load to cause the load to decrease power consumption or transfer to lessen the chance of the energy consumption exceeding the limit. In some embodiments, the system includes a signal generator, communications bus, communications interface (e.g., communications interface 4314), or any other suitable components for generating a software signal (e.g., included in a gateway), electrical signal, optical signal, wireless signal, any other suitable signal, or any combination thereof. In some embodiments, step 4606 includes the system transmitting the one or more control signals over one or more communications links. The one or more control signals may be transmitted over a cable (e.g., a multiconductor cable), a communications bus, one or more wires, one or more fiber optics, one or more wireless signals (e.g., transmitted and received by antennas), control circuitry (e.g., of a PCB), any other suitable communications link, or any combination thereof. In an illustrative example, step 4606 may include the system sending one or more control signals to communications-enabled loads (e.g., appliances, HVAC system) to reduce consumption.

Step 4608 includes the system generating one or more control signals, corresponding to one or more controllable elements, to interrupt current to loads, sources, or a combination thereof. In an illustrative example, the one or more controllable elements may include controllable breakers and/or controllable relays of any of branch circuit(s) 4330 of FIG. 43 , controllable circuit devices 114 of branch circuits 156 of FIG. 1 , relays 3114 and 3124 of FIG. 31 , relays 3230 and 3231 of FIG. 32 , or any other controllable elements. Each control signal may include an analog signal, a digital signal (e.g., in serial or parallel, or a combination thereof), a message (e.g., transmitted using any suitable protocol), a relay/switch signal (e.g., on/off, or one position of a multi-position switch), a waveform (e.g., having a frequency, phase, amplitude, and/or other characteristic), a pulse-based signal (e.g., a pulse-width modulated signal, a pulse-density modulated signal), any other suitable signal, or any combination thereof. In some embodiments, at step 4608, the system generates a control signal corresponding to a controllable element to interrupt current flow to loads, interrupt a branch circuit, or otherwise lessen the chance of the energy consumption exceeding the limit. In some embodiments, the system includes a signal generator, communications bus, communications interface (e.g., communications interface 4314), or any other suitable components for generating a software signal (e.g., included in a gateway), electrical signal, optical signal, wireless signal, any other suitable signal, or any combination thereof. In some embodiments, step 4608 includes the system transmitting the one or more control signals over one or more communications links. The one or more control signals may be transmitted over a cable (e.g., a multiconductor cable), a communications bus, one or more wires, one or more fiber optics, one or more wireless signals (e.g., transmitted and received by antennas), control circuitry (e.g., of a PCB), any other suitable communications link, or any combination thereof. In an illustrative example, step 4608 may include the system sending one or more control signals to relays or other actuators to interrupt current flow to and from loads and sources.

Step 4610 includes the system determining whether energy consumption is within, less than, or otherwise not exceeding the limit. In some embodiments, the system performs the same determination at step 4610 as step 4602 to determine whether the energy consumption exceeds the limit, is within the limit, or otherwise whether to generate control signals for loads and sources. In some embodiments, the system performs step 4610 after each of steps 4604, 4606, or 4608 to determine if whether energy consumption is within the limit. For example, the system may perform step 4604 and then check the results at step 4610. Further, if the energy consumption is not within the limit, the system may proceed to step 4606 and then check again at step 4610. Further, if the energy consumption is still not within the limit, the system may proceed to step 4608 and then check again at step 4610. In some embodiments, if the system determine that the energy consumption is within the limit (e.g., at least one of steps 4604, 4606, or 4608 was successful), then the system may proceed to normal operation at step 4699, wherein the system need not generate control signals to affect production or consumption.

It will be understood that the steps of process 4600 may be rearranged, omitted, or otherwise modified in accordance with the present disclosure. For example, any or all steps 4604, 4606, and 4608 may be performed in parallel or in an order differing from that illustrated in FIG. 46 .

In some embodiments, process 2500 of FIG. 25 or process 4600 of FIG. 46 may be used by control systems or algorithms to adjust power management by, for example, shifting loads in time (e.g., by disconnecting a load for a period of time and then reconnecting it and allowing it to draw power) or reducing the rate of draw of loads whose draw is adjustable (e.g. by reducing the available current of a J1772 electric vehicle charger).

In some embodiments, the present disclosure is directed to a programmable control system (e.g., system 4500) configured to limit net power flow to a set threshold at given physical point(s) of a behind-the-meter (BTM) power distribution system (e.g., point of interconnection of a property to the electric utility power distribution grid), via a monitoring and multilayered control architecture. For example, control elements (e.g., actuators 4523 of FIG. 45 or any other suitable controllable elements such as relays) are used to modulate current and/or power to and from loads, energy storage, and generation sources in response to control system algorithms. The system (e.g., system 4520) may be configured to modify duty cycles, modify setpoints, electrically isolate groups of loads and/or sources from the broader system, turn loads and/or sources on and off, perform any other suitable functions, or any combination thereof.

In some embodiments, the system (e.g., system 4520) prevents overload of, or otherwise manages, current-carrying conductors and electrical bussing within the system, such as to avoid upgrades to electrical service conductors when adding new loads and/or behind-the-meter generation sources. The system (e.g., system 4520) may also be configured for, for example: (i) limiting apparent peak demand at the site electrical meter, such as for utility bill charge reduction or for ensuring stability of the electrical grid when acting in aggregate with other similar systems; and (ii) improving system efficiency, such as to make preferential use of on-site power generation sources to power loads (e.g., versus drawing from a local electric power system (EPS) such as a utility grid); (iii) ensuring stability of the electrical grid when acting in aggregate with other systems (e.g., frequency regulation, voltage regulation, such as by Demand Response (DR) control of loads and sources); and (iv) interrupting electrical issue that may present safety risks such as electrical short circuits within a home or structure.

In some embodiments, the system (e.g., system 4520) may be used to serve residential or commercial sites, as the fundamental architecture of monitoring and control may be the same or similar. Metering and actuation devices, for example, would only need to be scaled to meet the required current and voltage needs of the site. Similarly, the system (e.g., system 4520) may be applied to single-phase, two-phase, split-phase, three-phase electrical systems, any other suitable systems, or any combination thereof.

In some embodiments, the system (e.g., a control system, control circuitry, a module, a device) includes:

-   -   a programmable controller (e.g., programmable controller 4525 of         FIG. 25 );     -   software control algorithms (e.g., computer-executable         instructions stored in memory);     -   power metering of selected feeder(s), bussing, and individual         circuit(s) such as branch circuits (e.g., using actuators 4523         or communication with devices);     -   sensor and sensor interfaces for measurement (e.g.,         instantaneous measurement) of current (e.g., branch current, bus         current), voltage, frequency, power factor, real and reactive         power, energy accumulation over time, any other suitable power         quality measurements, any other suitable power quantity         measurements, or any combination thereof (e.g., power monitor         4524 of FIG. 45 );     -   physical control elements (e.g., OCPDs 4522 and actuators 4523         of FIG. 45 ) incorporated within the control system such as         relays, contactors, controllable breakers, or switches for         interrupting alternating current (AC) circuits and/or direct         current (DC) to directly interrupting power flow or for         interrupting logic signals to external controllers (e.g., the         elements may be controlled directly by the programmable         controller and need not rely on communication to a third party         device);     -   overcurrent protection devices (e.g., OCPDs 4522 of FIG. 45 )         such as circuit breakers or fuses (e.g., which can be installed         within the device or externally);     -   a user interface for programming control settings and viewing         system operational status (e.g., which may be coupled to, or         integrated as part of, programmable controller 4525);     -   communication interfaces (e.g., hardware which may be coupled         to, or integrated as part of, programmable controller 4525,         and/or software including computer readable instructions stored         in memory) to interconnect with communication-enabled ‘smart’         loads (e.g., of loads and sources 4530), generation sources         (e.g., of loads and sources 4530 and/or sources 4550), load         devices including an input/output interface, any other suitable         devices, or any combination thereof such as wireless radios         (e.g., Wi-Fi, Bluetooth, Cellular, Zigbee, or ZWave) and/or         physical interfaces for wired communication connections such as         using Ethernet TCP/IP, USB, modbus, RS-485, CANbus, power-line         communications, or other suitable techniques.

In some embodiments, the system (e.g., system 4520) may incorporate distributed, networked control elements which communicate to the centralized control system for the purposes of granular monitoring and control. The networked control elements may respond to control requests from the centralized control system from within the area electric power system (EPS) or externally via remote communications from entities such as electric utilities or fleet aggregators to schedule their operation, modify duty cycle or setpoints, modulate current flow, perform any other suitable action, or any combination thereof.

In some embodiments, the system (e.g., system 4520) may include multiple devices operating in conjunction with each other to achieve a desired system-level control result (e.g., a control optimization).

In some embodiments, direct communication to distributed elements (e.g., loads, load groups, generation sources, generation source groups) may be transmitted over wired or wireless (e.g., local network or through Internet) communication routes. For example, loads and sources 4530 may be communicatively coupled to programmable controller 4525 via a communications network. For example, steps 4604, 4606, and 4608 of process 4600 of FIG. 46 may include such direct communications.

In some embodiments, the system (e.g., system 4520) monitors power flow and other related or otherwise suitable signals such as rate of change of frequency, voltage, current at a circuit and/or sub-circuit level (e.g., using power monitor 4524) in addition to monitoring of feeders and bussing allows the system to determine which load(s) or group(s) of loads must be modulated or interrupted to limit net power as a given point in the system (e.g., at step 4608 of process 4600 of FIG. 46 ). Preferential modulation of loads and/or sources (e.g., steps 4604 and 4606 of process 4600 of FIG. 46 ) may follow a hierarchy, included in an illustrative example as:

(1) the controller communicates directly with individual loads and generation sources (e.g., of loads of sources 4530) to request they modify their operating profile, such as by coordinating time when loads cycle on/off in relation to other loads or available onsite generation (e.g., at steps 4604 and 4606 of process 4600 of FIG. 46 ). By coordinating operation of loads, sources, or both net power flow at the controlled point(s) is maintained at the set point. In some embodiments, the controller (e.g., programmable controller 4520) communicates directly with on-site energy storage or generation sources (e.g., a home battery system or solar photovoltaic system of loads and sources 4530) to request that additional source current be provided to offset consumption from the load. Where generating sources and loads both are located on the same side of the controlled point(s), net power at the controlled point(s) is maintained at the set point such as by coordinating time when loads cycle on/off in relation to other loads or available onsite generation, or by reducing the power draw of a variable-rate load such as an electric vehicle charger. In some embodiment, the operating profile or modified operating profile may be modified, displayed, or both using energy application 4351 of FIG. 43 or GUI 4400 of FIG. 44 .

(2) where the above inter-device software control layers do not bring power flows within the set limits, circuit controllers and/or other actuators (e.g., actuators 4523) directly connected to the control system (e.g., programmable controller 4525) at the distribution circuit level electrically isolate loads/sources from contributing to power flow on the controlled conductor following pre-determined sequences (e.g., user-defined shut-off sequences). By interrupting connection of loads and/or sources (e.g., at step 4608 of process 4600 of FIG. 46 ), net power flow at the controlled point(s) is limited to the set point (e.g., energy consumption is maintained within limits).

(3) as a final or otherwise additional hardware fail-safe, overcurrent protection devices (OCPDs) such as thermal-magnetic breakers or fuses (e.g., OCPDs 4522 of FIG. 45 ) are installed per electrical code to interrupt circuits or groups of circuits based on a defined current-time relationship to prevent thermal overload at given points of the electrical distribution system. Interruption of the connected loads and/or sources provides a final hardware protection against overcurrent.

In some embodiments, the multilayered controls scheme creates multiple-redundant mechanisms to achieve the desired control outputs based on feedback from the controller's power monitoring sensors and control algorithms (e.g., process 4600 of FIG. 46 as implemented by system 4520 of FIG. 45 ). For example, steps 4604, 4606, and 4608 may be performed sequentially (e.g., as illustrated, or in any suitable order), in parallel, or a combination thereof. For example, the system may perform step 4604 and then check whether power consumption exceeds power capacity at step 4610. If so, then the system may proceed to step 4606, and if not, the system may proceed to normal operation. After performing step 4606, the system may again check whether power consumption exceeds power capacity at step 4610. If so, then the system may proceed to step 4608, and if not, the system may proceed to normal operation. After performing step 4608, the system may again check whether power consumption exceeds power capacity at step 4610. If so, then the system may further modify operation at any of steps 4604, 4606, or 4608 (e.g., by modifying setpoints, turning off additional branch circuits, or further increase power capacity of an energy source), and if not, the system may proceed to normal operation.

In some embodiments, once the power/current setpoint is achieved by modulating BTM loads and/or sources, the controller (e.g., programmable controller 4525) evaluates the information from the metering system (e.g., at a regular interval, or in response to an event), and determines (e.g., decides) when to return to, or otherwise enter, another operating mode. For example, when energy consumption is within limits (e.g., as determined at step 4610), the controller may turn loads that have been shed back on, or return to an original setpoint (e.g., normal operation of step 4699 of FIG. 46 ). In a further example, if the controller (e.g., programmable controller 4525) returns loads and setpoints to original operation and that does not result in power flows exceeding set limits, the controller need not take further action (e.g., other than monitoring by power monitor 4524 in normal operation of step 4699). If returning the loads, sources, and setpoints does result in power flows exceeding set limits, the controller may follow any or all of the hierarchical steps described above (e.g., of process 4600) within predetermined limits.

In some embodiments, inputs such as physical and electrical system layout, current-carrying capacities of electrical conductors, ratings of overcurrent protection devices, any other suitable information, or any combination thereof are set at the time of installation by a user interface (e.g., such as smartphone App) and settings may be updated over time as system elements are added, removed, or otherwise modified. Settings may be stored in local memory of the controller (e.g., programmable controller 4525), for example, or otherwise be accessible to the controller as reference information. In some embodiments, read access, write access, or both for some settings is regulated using security provisions such as restricted passwords, specification of authorized users, or other protective measures.

In some embodiments, the controller (e.g., programmable controller 4525) is configured for optimizing of targets and constraints by determining, for example, setpoints, schedules, charge levels, stored energy, requirements related to the utility grid, any other suitable user preferences, or any combination thereof. In some embodiments, users input preferences may be received (e.g., at an input interface) for a sequence of control, which may include reducing or otherwise ceasing one appliance's load before another load.

The control system (e.g., system 4520 of FIG. 45 ) may inform the user such as by a notification through a user interface (e.g., via a smartphone App) of any autonomous action taken by the control system. For example, energy application 4351 of FIG. 43 may be configured to indicate actions taken by the system (e.g., control system 4310, which may be similar to system 4520 of FIG. 45 ).

In some embodiments, the controller (e.g., programmable controller 4525) may implement software that builds predictive models of system operation. For example, the system (e.g., system 4520) may use the models to anticipate a likelihood of power/current flow at points in the system, take preventative action (e.g., such as scheduling operation of loads and generation sources in a coordinated fashion), notify a user to edit preferences (e.g., temperature setpoints for HVAC, charge profiles for electric vehicles, battery reserve capacity, any other suitable preferences, or any combination thereof), any other suitable action, or any combination thereof. In some embodiments, the system (e.g., system 4520) implements a model that may incorporate or otherwise access local weather information, indoor temperature, solar forecasting, user behavior (e.g., of one or more users, statistical determinations based on many users), user schedule, any other suitable reference information, or any combination thereof.

FIG. 47 is a flowchart of illustrative process 4700 for modifying operation of loads and sources, in accordance with some embodiments of the present disclosure. Any of the suitable systems or controllers of the present disclosure may implement process 4700, or suitable portions thereof. For example, system 100 (e.g., or onboard computer 118 thereof) of FIG. 1 , gateway 503 of FIGS. 6-16 , control system 4310 of FIG. 43 (e.g., or control circuitry 4311 thereof), system 4520 of FIG. 45 , or any other suitable system may implement process 4700. In an illustrative example, process 4700 may be an example of process 4600 of FIG. 46 .

Step 4702 includes the system determining an indicator corresponding to a limit in power capacity. In some embodiments, at step 4702, the system retrieves, receives, or otherwise accesses reference information 4790, which may include setpoint values, power capacity limits or ranges, current limits or ranges, temperature limits or ranges, any other suitable information, or any combination thereof. In some embodiments, at step 4702, the system retrieves, receives, or otherwise accesses sensor information 4791, which may include sensor signals, calculated values based on sensor signals, modeled values, any other suitable information, or any combination thereof. For example, the indicator may include an energy consumption (e.g., calculated based on sensed currents), a power generation capacity (e.g., reduction in electrical power capacity of a source), a loss of an energy source, a change in one or more limits, or a combination thereof. In some embodiments, the system may determine an indicator indicative of reduced electrical power capacity, increased consumption, reduced limits of operation, any other suitable indicator, or any combination thereof.

Step 4704 includes the system identifying one or more loads, energy storage devices, sources, or a combination thereof that may be controlled (e.g., loads and sources 4530 in communication with programmable controller 4525). The system may identify one or more appliances, one or more generators (e.g., a solar PV generating array), one or more energy storage devices (e.g., battery systems, which can be a load or a source depending on operation), based on load preferences, a predetermined hierarchy, user preferences, any other suitable criteria, or any combination thereof. The system may identify a device at step 4704 based on a hardware identification, a network identification, an identifier stored in memory, which branch circuit the device is coupled to, any other suitable identifying information, or any combination thereof. In some embodiments, step 4704 may include identifying one or more EV chargers (e.g., included in loads and sources 4530 or loads and sources 4540).

Step 4706 includes the system identifying one or more modifications that may be applied to sources, loads, branch circuit, or a combination thereof. Modifications may include modified setpoints, de-powering and powering devices, alternating operation of devices, scheduling device operation, any other suitable change from normal operation, or any combination thereof. In some embodiments, the modification depends on the type or characteristics of the identified loads, sources, or energy storage devices of step 4704.

Step 4708 includes the system communicating with one or more loads or sources to request a modified operating profile. In some embodiments, step 4708 may include step 4604, step 4606, or both, for generating control signals for one or more loads, sources, or a combination thereof. In some embodiments, step 4708 includes sending messages or information, receiving messages or information, or a combination thereof to and from one or more devices communicatively coupled to the system (e.g., any of loads and sources 4530 of FIG. 45 ).

Step 4710 includes the system isolating one or more loads or sources from contributing to power flow. In some embodiments, at step 4710, the system generates one or more control signals (e.g., a plurality of control signals) for controlling one or more controllable elements corresponding to one or more branch circuits. For example, the system may disconnect one or more loads (e.g., an appliance, EV charger, transformer coupled to a load, or any other load), sources, or both by controlling branch relays to open the respective branch circuit. In a further example, the system may, at step 4710, turn off one or more devices to isolate the one or more devices from the AC bus (e.g., or other loads and sources).

Step 4712 includes the system applying at least one load and/or source model. The model may be stored in suitable memory and may include, for example, parameter values, functions (e.g., an equation), logic operations, vector operations, any other suitable information, or any combination thereof. For example, in some embodiments, a model may simulate behavior of a load or source based on time, temperature, use, location, device characteristics, user characteristics, any other suitable input, or any combination thereof. Accordingly, the system may determine one or more inputs (e.g., a set of inputs), provide the one or more inputs to the model, and extract one or more outputs (e.g., a set of outputs) that correspond to energy consumption, current draw, operating temperature (e.g., of a winding, power electronics, or other electronic component), voltage drop, frequency, phase shift, impedance, any other suitable output, or any combination thereof.

Step 4714 includes the system causing electrical power to or from loads or sources to be modified based on any or all of steps 4702, 4704, 4706, 4708, 4710, and 4712. In some embodiments, steps 4702, 4704, 4706, 4708, 4710, and 4712 along with step 4714 define a second operating mode wherein one or more loads or sources is limited other than by main or branch circuit OCPDs (e.g., by controlled relays or modified operation). Step 4714 may include modifying setpoints (e.g., modifying an EV charging rate), disconnecting circuits or device, turning devices on or off, isolating one or more first circuits/devices from other circuits/devices, modifying an operating schedule or operating range, any other suitable modification to limit an energy consumption from exceeding an energy supply, or any combination thereof.

Step 4716 includes the system monitoring current flow in branch circuits, lines (e.g., main busbars), or a combination thereof. In some embodiments, step 4716 includes step 4610 of FIG. 46 . In some embodiments, at step 4716, the system receives one or more sensor signals and determines, based on the one or more sensor signals, a state of the electrical system. For example, the system may monitor branch currents based on branch current sensors, a bus current based on one or more main current sensors, or a combination thereof. In a further example, the system may send and receive messages or other information to and from one or more devices (e.g., of loads and sources 4530) to determine a state of each device.

Step 4718 includes the system returning to a normal mode, or otherwise normal operation (e.g., a first mode). In some embodiments, the system returns to the normal mode based on monitoring at step 4716 (e.g., based on one or more sensor signals). In some embodiments, the system returns to normal operation in response to a received input or event (e.g., an indication from another device or server to return to normal mode). In some embodiments, the system returns to normal operation after a predetermined amount of time has elapsed (e.g., return to normal mode in 10 minutes, 30 minutes, 1 hour, or any other suitable time duration) and at a predetermined time (e.g., at midnight, at noon, at some other clock time). Step 4718 may include generating a control signal to a controllable element (e.g., to close a relay to connect a branch circuit), ceasing a control signal to a controllable element (e.g., allowing a relay to connect a branch circuit), generating a message or signal indicating to a device to return to normal mode, resetting or otherwise adjusting a setpoint, resetting or otherwise adjusting a limit or threshold, or a combination thereof. In some embodiments, the system may implement a set of computer-readable instructions that correspond to normal mode. In an illustrative example, process 4700 may start with the system in normal mode, and end with a return to normal mode after responding to a limiting condition (e.g., a fault or interruption in power capacity, overconsumption, or other suitable condition).

Step 4720 includes the system remaining in a limiting mode, or otherwise modified operation (e.g., a second mode). In some embodiments, the system remains in the limiting mode until receiving an input or detecting an event (e.g., an indication from another device or server to return to normal mode). In some embodiments, the system remains in the limiting mode until a predetermined amount of time has elapsed (e.g., return to normal mode in 10 minutes, 30 minutes, 1 hour, or any other suitable time duration) and until a predetermined time (e.g., at midnight, at noon, at some other clock time). Step 4720 may include generating a control signal to a controllable element (e.g., to open a relay to disconnect a branch circuit), ceasing a control signal to a controllable element (e.g., allowing a relay to disconnect a branch circuit), generating a message or signal indicating to a device to remain in limiting mode, resetting or otherwise adjusting a setpoint, resetting or otherwise adjusting a limit or threshold, or a combination thereof. In some embodiments, the system may continue to implement a set of computer-readable instructions that correspond to limiting mode. In some embodiments, wherein the system determines that energy consumption in the limiting mode does not exceed production or otherwise exceed a limit, the system determines to return to an unmodified operating profile at step 4720 based on monitoring the current flow at step 4716.

In some embodiments, process 4700 includes the system (e.g., programmable controller 4525) communicating with one or more electrical loads or generation sources to request a modified operating profile (e.g., from loads and sources 4530) at step 4708, isolating one or more second loads or generation sources from contributing to power flow at step 4710, and monitoring current flow in the electrical system (e.g., branches, mains, loads, sources) at step 4716.

In an illustrative example, the system may detect an indicator at step 4702 corresponding to a limit of power capacity, communicate with the one or more first electrical loads or sources in response to the indicator at step 4708, and isolate one or more second loads or generation sources is in response to the indicator at step 4710.

In an illustrative example, in some embodiments, the system operates in a first operating mode where electrical power is limited by protection devices (e.g., normal mode of step 4718). The system may identify an indicator corresponding to a reduced capacity of electrical power at step 4702, and then enter a second operating mode (e.g., shown as portions of process 4700 and as indicated by step 4720) that includes retrieving reference information including load preferences and limits (e.g., at step 4702) and managing one or more loads to limit electrical power based on the reduced capacity and based on the reference information at any or all of steps 4702, 4704, 4706, 4708, 4710, and 4712.

In an illustrative example, in some embodiments, the system manages an electrical system by determining one or more limits on electrical current or electrical power at step 4702 based on reference information 4790, identifying one or more loads to be modified at step 4704, identifying one or more modifications corresponding to the one or more loads at step 4706, and causing electrical power to the one or more loads to be modified based on the one or more modifications at step 4714. In some embodiments, the one or more modifications of step 4706 include a change to a setpoint of an operating parameter (e.g., current, temperature, duty cycle, or other suitable parameter). In some embodiments, the one or more modifications of step 4706 include turning a load of the one or more loads off (e.g., to reduce energy consumption). In some embodiments, the system identifies the one or more modifications at step 4706 by accessing reference information 4790, which includes at least one of user preference information, historical usage information, or predetermined settings. In some embodiments, the one or more loads include one or more appliances (e.g., smart-appliances communicatively coupled to the controller, as illustrated in FIG. 45 ). In some embodiments, the one or more loads include one or more branch circuits. In some embodiments, the system identifies an event and determines the one or more limits based at least in part on the event. The event may include, for example, a fault, a user input, an input received from another device (e.g., a remote server), an indication from a power monitor (e.g., power monitor 4524 of FIG. 45 ), any other suitable event, or any combination thereof.

In an illustrative example, in some embodiments, the system identifies a reduced electrical power capacity of the electrical system at step 4702, applies a load model to determine a set of modifications to one or more loads coupled to the electrical system via a plurality of branch circuits at step 4712 (e.g., where each of the plurality of branch circuits is controllable), and modifies operation of the one or more loads based on the load model at step 4714.

In some embodiments, the systems (e.g., energy management systems) and panels of the present disclosure are configured to manage energy usage, detect faults, and respond to faults. For example, the techniques of the present disclosure may allow for more complete use of data and capabilities presented by an energy management system (“EMS”) in order to improve security and quality of life for homeowners and business personnel. The present disclosure may be implemented using an integrated smart panel, an EMS module, a building constellation of distributed modules (e.g., configured to perform energy management), any other suitable hardware configuration, or any combination thereof. To illustrate, many things can go wrong in a house without the homeowner being aware of, or able to mitigate, the hazard. The systems and methods of the present disclosure may provide for using data and control capabilities of the EMS to address some concerns such as (i) using visibility into electrical phenomena in the house, third party data (e.g., environmental information such as weather data or indoor air temperature data), or a combination thereof to provide situational awareness to the homeowner, and (ii) taking advantage of control capabilities of the EMS to respond automatically to hazards, threats, and inconveniences. In some embodiments, the EMS can integrate with a plurality of devices in the home and can also collect extensive metadata about the house to provide unique or otherwise improved capabilities to both develop situational awareness and respond to residential fault scenarios. FIGS. 48-51 illustrate some aspects of fault detection and response, in accordance with some embodiments of the present disclosure.

FIG. 48 is a block diagram of illustrative system 4800 including an integrated electrical panel 4810, appliances 4820, 4830, and 4840, and sensors 4850, in accordance with some embodiments of the present disclosure. While illustrated as part of an integrated electrical panel, controller 4812 may be implemented as an EMS separate from an electrical panel, an EMS module, one EMS module of a plurality of modules, or any other suitable arrangement. For example, system 4800 need not be limited to or otherwise included as part of an integrated electrical panel. As illustrated, integrated electrical panel 4810 includes electrical panel 4811 (e.g., busbars, neutral bars, breakers, relays, sensors, enclosure, deadfront), controller 4812, and optionally current sensors 4814. For example, current sensors 4814 may be integrated into electrical panel 4811, as illustrated in FIGS. 31-42 , and, in some embodiments, need not be included as a separate component. Backend 4860 is communicatively coupled to controller 4812 via a communications link (e.g., via a network). As illustrated, appliances 4820 include smart appliances that include communications interfaces for communicating with controller 4812 and may be, but need not be, electrically coupled to electrical panel 4811. As illustrated, appliances 4830 are plugged in or otherwise electrically coupled to branch circuits of electrical panel 4811. Appliances 4830, as illustrated, include non-smart appliances (e.g., not communicatively coupled to controller 4812, without communications interfaces). Appliances 4840 include appliances electrically coupled to branch circuits or otherwise busbars of electrical panel 4811, and that also include communications interfaces to communicate with controller 4812. To illustrate, integrated electrical panel 4810 may be the same as or otherwise similar to system 4520 of FIG. 45 (e.g., and may be configured to implement either or both of processes 4600 and 4700), control system 4310 with AC bus 4320 and branch circuits 4330, the panel 4200 of FIG. 42 , system 3200 of FIG. 32 , electrical panel 3110 of FIG. 31 , any of the panels of FIGS. 5-16 , or panel 102 of FIG. 1 . In an illustrative example, controller 4812 may be the same as, similar to, or integrated as part of control system 4310 (e.g., or control circuitry 4311 thereof), which be an EMS configured to manage energy consumption (e.g., and may be but need not be included in an electrical panel).

In some embodiments, system 4800 may be configured to perform data collection and analysis. For example, an EMS controller (e.g., controller 4812, which includes processing circuitry) may be configured to collect high-resolution current measurements from current sensors 4814 (e.g., CTs, shunts, or other suitable sensors) attached to each branch circuit of electrical panel 4811. Controller 4812, electrical panel 4811, or both may include electromechanical relays arranged in series with each branch circuit to allow connection/disconnection of power to those circuits (e.g., to connect/disconnect busbars from loads). In some embodiments, controller 4812 is configured to collect or otherwise determine metadata associated with the homeowner. For example, data may be collected about the breaker panel itself (e.g., electrical panel 4811) such as main breaker rating, individual breaker ratings and labels, any other suitable information, or any combination thereof. In some embodiments, controller 4812 may collect data about appliances in the home (e.g., any or all of appliances 4820, 4830, and 4840). For example, metadata associated with appliances may include fields such as an identifier (e.g., a name, ID number), which branch circuit(s) the appliance is associated with, the appliance's location in the house or building, make and model information, year of manufacture, year of installation, maintenance history, ratings, square footage information, any other suitable information, or any combination thereof. In a further example, controller 4812 may be configured to determine or retrieve third party data such as weather data or any other suitable information, or any combination thereof.

In some embodiments, controller 4812 is configured to identify, receive, or otherwise determine appliance-specific metadata and models. In some embodiments, controller 4012 downloads information from a central database of additional metadata about one or more appliance (e.g., of appliances 4820, 4830, and 4840). For example, controller 4812 may look up an appliance's nameplate specifications from its make, model, and year of manufacture, in order to accurately distinguish between normal and abnormal electrical signatures of the appliance. In some embodiments, controller 4812 may download various forms of digital representation of the appliance including, for example:

-   -   textual metadata about the appliance;     -   physics models representing the appliance;     -   logical models (e.g., state machines, pushdown automata)         representing the appliance's functional behavior;     -   datasets representing specific fault modes of the appliance,         including such contents as text labels, electrical signatures as         time-series sample, Bayesian priors, probability distributions         over time, causal factors (e.g., salt, humidity), location of         installation (e.g., indoor, outdoor, room, region, orientation),         exposure to events such as earthquakes; and/or     -   machine-learning models that act as classifiers against the         fault scenarios above.         Each of these digital representations may be individualized         against the specific make and/or model of the appliance, or they         may be generic across many or all appliances within that         appliance type (e.g., one model for all mini-split air         conditioners).

In some embodiments, controller 4812 is configured to recognize an appliance. For example, in some embodiments, controller 4812 is configured to use labels provided by the user (e.g., homeowner, facility manager) to identify one or more appliances connected to each branch circuit, which each may be metered by a current sensor of current sensors 4814. Controller 4812 may be configured to use characteristics of current draw on a circuit (e.g., periodicity, magnitude, frequency components) or machine learning algorithms to identify appliances connected on a particular circuit (e.g., an indexed branch circuit). For example, in some embodiments, controller 4812 may use a disaggregation algorithm to distinguish electrical signatures of multiple appliances in order to monitor multiple appliances using a single current sensor of current sensors 4814 (e.g., multiple appliances may be electrically coupled to a branch circuit). In some embodiments, controller 4812 is configured to verify the user's labels against the observed electrical signature of the appliance and prompt the user for clarification if the appliance label and inferred appliance type conflict (e.g., a user labels an AC unit as a dishwasher). In some embodiments, controller 4812 prompts the user for additional appliance metadata if it detects new and/or unlabeled appliances on the circuit (e.g., based on disaggregation, or identifying the appliance via a communications link).

In some embodiments, controller 4812 is configured to implement sensor fusion and behavioral analysis. In some embodiments, controller 4812 is configured to collect data from networked and/or wired sensors (e.g., sensors 4850) such as smoke detectors, carbon monoxide (CO) detectors, air quality sensors, particulate sensors, barometers, ambient light sensors, temperature/humidity sensors, water flow sensors and/or leak detectors, microphones, IR and other photosensors, occupancy sensors, any other suitable sensor, or any combination thereof. Controller 4812 may communicate with sensors 4850 over a local area communications network, such as a 2.4 GHz/900 MHz wireless mesh and/or powerline communications. In some embodiments, sensors from the same product suite may act as wireless mesh nodes to bolster signal strength. Data from suitable sensors (e.g., of sensors 4850) may be combined with electrical and current data to form a broader picture of what's happening in the home or building. For example, controller 4812 may use data from some sensors to confirm proper function of other sensors, such as by monitoring the current consumption (e.g. using a current sensor of current sensors 4814) of a smoke detector to confirm that the smoke detector is functional. In some embodiments, controller 4812 is configured to determine (e.g., impute) human occupancy and/or activity in the home based on current consumption (e.g., from lighting or other appliances coupled to branch circuits) in addition to direct use of occupancy sensors (e.g., of sensors 4850). For example, controller 4812 may be configured to implement sensor fusion by combining a measured current or set of currents along with other sensor or data signatures. To illustrate, an EMS may be configured to determine (e.g., recognize) lights being turned off based on a measurement of current consumption (e.g., at the corresponding branch circuit current sensor), and then cause a smart lock to actuate afterward (e.g., the EMS may determine with high-confidence that the “user has left the house” signature is exhibited). In a further example, controller 4812 may communicate with smartphone sensors to implement geo-fencing to determine if a user device is in or near a predetermined region (e.g., the building, a room, an area). To illustrate, controller 4812 may be configured to monitor current sensors 4814, sensors 4850, user device location, third party information, any other suitable information, or any combination thereof to identify an event or signature. In some embodiments, for example, controller 4812 is configured to learn typical patterns of electricity consumption in the house or building in order to be able to identify abnormal activity (e.g., based on timing, current consumption, or branch circuit).

In an illustrative example, current sensors 4814 may transmit high-resolution voltage measurements, current measurements, or both to controller 4812, which may be configured to sample the signals at any suitable frequency (e.g., for analog signals), or otherwise receive the signals, and store the measurements in memory. Controller 4812 may be configured to communicate with backend 4860, to receive information or instructions (e.g., setpoints, limits, statistical information, reference information), send information (e.g., data, preferences, alerts), transmit telemetry information, transmit fault information (e.g., a digital representation of the fault or event), transmit any other suitable information, or any combination thereof. Controller 4812 may be configured to communicate (e.g., via network) with one or more smart appliances (e.g., appliances 4820 or 4840), to transmit telemetry information, commands (e.g., on/off, setpoints, consumption targets, timing schedules), any other suitable information, or any combination thereof. Controller 4812 may be configured to communicate (e.g., via network) with one or more sensors 4850, to transmit direct analog readings, digital signals, any other suitable information using any suitable protocol, or any combination thereof.

In some embodiments, integrated electrical panel 4810 may include a controller (e.g., controller 4812) that includes an Internet-connected computer or processing equipment. To illustrate, the controller may be configured to maintain a local area communications network, which in some instantiations may include a 900 MHz/2.4 GHz wireless mesh network, and in others may include powerline communications. In some embodiments, controller 4812 may be integrated with or otherwise coupled to one or more current and voltage sensors to monitor the flow of electricity through a residential building (e.g., in branch circuits thereof). In some embodiments, integrated electrical panel 4810 or controller 4812 thereof may be integrated with or otherwise coupled to one or more electromechanical relays or other switching devices to disconnect circuits in the home. In some embodiments, integrated panel may be installed in a wall or another electrical panel of a home or facility. In some embodiments, sensors 4850 include residential sensors such as, for example, smoke detectors, carbon monoxide (CO) detectors, air quality/particulate matter sensors, barometer, ambient light sensor, temperature/humidity sensors, water flow or leak detectors, microphones, IR and other photosensors, occupancy sensors, any other suitable sensor, or any combination thereof, which are connected to the communications network and are configured to send sensor data over the network to the energy management controller.

In some embodiments, controller 4812 is configured to lessen or eliminate the need for redundant IoT software stacks and/or communications hardware components in a sensor. For example, controller 4812 may be configured to transmit sensor measurements and events to the Internet. In a further example, controller 4812 may be configured to store telemetry and/or data from the sensor in the backend (e.g., backend 4860). In a further example, controller 4812 may be configured to integrate controls and visualization for the sensor into a user interface (e.g., mobile app, web app implemented by controller 4812). In a further example, controller 4812 may be configured to send notifications to the homeowner in case of noteworthy events such as a smoke alarm going off. In a further example, controller 4812 may be configured to, in case of fire or other hazard to persons or property (e.g., water leak), disconnect power to appliances or circuits that may be causing, or vulnerable to, the hazard. In a further example, controller 4812 may be configured to perform sensor fusion to detect anomalous operation of household appliances (e.g., detect water flow to an appliance that is not operating) based on separate or unrelated sensors of sensors 4850 and or current sensors 4814. In a further example, controller 4812 may be configured to use occupancy detection specifically to detect unexpected power draw, either using occupancy sensors or inferring room occupancy from electrical measurements (e.g., room lighting power draw). In a further example, controller 4812 may be configured to use current and voltage sensing to verify correct functioning of a residential sensor (e.g., alert when a smoke alarm shows anomalous power draw). In a further example, controller 4812 may be configured to use sensors 4850 as wireless mesh nodes to bolster signal strength and/or extend the network throughout the house. In a further example, controller 4812 may be configured to take advantage of suitable synergies between devices. To illustrate, this integration of controller 4812 may allow for cost reduction and an increase in the reliability and customer value of residential sensors.

In some embodiments, data may be aggregated and analyzed at a central controller (e.g., the building's existing Energy Management System controller) to inform system-level operating decisions and optimization (e.g., for energy management, power management, occupant comfort, occupant health and safety). For example, this control may be real-time or involve intelligent algorithms which use data collected over time to inform operation. In some embodiments, controller 4812 may receive information from other controllers (e.g., associated with other houses in a neighborhood, a set of facilities, other suitable integrated electrical panels). For example, controller 4812, or a suitable collection of controllers (e.g., each similar to controller 4812), may be configured to achieve tariff optimization or cost, share data collected during respective monitoring, generate predictions based on or otherwise inferred from historical data, perform any other suitable function, or any combination thereof.

In some embodiments, controller 4812, a central controller, any other suitable controller, or any combination thereof may be configured to present notifications, alerts, insights, and/or data to an end user via an external graphical user interface (e.g., via a smartphone app, web dashboard, LCD screen display), via messages to a mobile phone, via a user interface on the device (such as LED lighting, screen, emitting sound), or through third party monitoring using an API.

In some embodiments, some or all components of systems of the present disclosure (e.g., system 4800) may be installed indoors or mounted on an internal surface such as wall or ceiling. This may include electronic components (e.g., printed circuit board assemblies containing sensors, power supplies, communication modules, microprocessors, energy metering circuitry, or other suitable electronics), an external housing (e.g., a plastic or metal enclosure), mounting bracket for ease of installation, user interfaces such as LED lighting, and button(s) (e.g., for setup, pairing, test, or other suitable function), any other suitable components, or any combination thereof. For example, devices that implement part or all of the system of the present disclosure may be provided in a variety of configurations with different combination of sensors to serve different use cases, or meet different price points.

In some embodiments, user-end system components of the present disclosure may be installed using hardwired AC (e.g. 120-240 VAC) or DC (e.g. 9-48 VDC) or using wiring to the building's electrical distribution center, which is sometimes required by building codes. An onboard energy source such as battery cell or supercapacitor can also be included in some embodiments. When installed in a home/building with a backup system (e.g., solar photovoltaic, backup battery, and/or standby generator), the system may communicate its location within the electrical wiring system for the purposes of, for example, energy management and/or ensuring power to the circuit is not interrupted. In some embodiments, the system (e.g., system 4800 or integrated electrical panel 4810 thereof) may be configured to or otherwise be capable of self-testing sensors to ensure full functionality.

In some embodiments, the system includes a plurality of sensors, a controller, and a plurality of actuators, installed into a residence (e.g., system 4800). The controller (e.g., controller 4812) may consist of a computer, microcontroller, or other programmable device. Sensors (e.g., sensors 4850 and current sensors 4814) may include electrical current and voltage sensors, smoke detectors, carbon monoxide (CO) detectors, air quality sensors, particulate matter sensors, a barometer, an ambient light sensor, temperature/humidity sensors, water flow or leak detectors, microphones, IR and other photosensors, occupancy sensors, or any other suitable sensor. The controller may communicate with the sensors through analog voltages/currents or through digital communications, including wireless (e.g., Zigbee) or wired (e.g., RS485) communications. Actuators may include electrical relays, valves, water sprinklers, speakers, and lights, which may be controlled by the controller. In some embodiments, the controller may collect data from a user by means of mobile application, touchscreen, web page, or other user interface. For example, this information may include information about the user's location. The controller may interface with appliances in the house using digital communications such as TCP/IP (e.g., for smart appliances of appliances 4820 or 4840).

In some embodiments, a controller (e.g., controller 4812) may use high-resolution time series data of current to individual appliances to detect faults or anomalous behavior in those appliances. For example, the controller may compare a measured current signature to a database of known faults or use machine learning algorithms such as neural networks trained against such a database to identify faults. The controller may communicate a need to repair the appliance to the user. In some embodiments, the controller may identify signs of likely faults, such as increased current draw or variability in current draw, through similar means, and alert the user similarly. In some embodiment, the controller may use anomaly detection algorithms to identify unusual patterns of current draw indicating incorrect use or faults not included in the controller's database and/or training set, and alert the user.

In some embodiments, a controller (e.g., controller 4812) is configured to respond to a fault or hazard event. For example, electrical panel 4811 may include at least one electrical circuit, and system 4800 may include at least one sensor (e.g., of current sensors 4814 and/or sensors 4850). Controller 4812 may include processing circuitry coupled to the at least one electrical circuit (e.g., a branch circuit) and to the at least sensor. The controller may be configured to receive sensor data from the at least one sensor, determine the fault or hazard event based on the sensor data (e.g., at step 4908 or 5008), and cause a change in current being supplied to at least one electrical circuit in the electrical panel in response to determining the fault or hazard event (e.g., by actuation a relay at step 4921 or sending a control signal at step 4922).

FIG. 49 is a flowchart of illustrative process 4900 for detecting and responding to a fault, in accordance with some embodiments of the present disclosure. For example, process 4900 may be implemented by system 4800 (e.g., controller 4812 thereof) to detects faults or other events of concern, and determine a response.

At step 4902, the system (e.g., controller 4812) measures current (I), voltage (V), or both for each branch circuit of an electrical panel (e.g., electrical panel 4811). For example, controller 4812 may determine a present power consumption, consumption profile (e.g., a temporal pattern or duration), or other suitable characteristic using one or more of current sensors 4814 corresponding to one or more branch circuits. In some embodiments, step 4902 may include taking measurements of voltage, current, or both corresponding to one or more branch circuits, and transmitting the measurements to controller 4812. The measurements may be communicated as analog signals, digital signals, or a combination thereof.

At step 4904, the system (e.g., controller 4812) collects data from one or smart appliances (e.g., appliances 4820 or 4840). In some embodiments, a smart appliance may include processing circuitry configured to control operation of the appliance, perform telemetry corresponding to operation of the appliance (e.g., using one or more sensors), log and analyze data (e.g., captured during operation or diagnostics), send alert information or data, receive commands, communicate with one or more other devices (e.g., a user device such as user device 4350 of FIG. 43 ), perform any other suitable actions, or any combination thereof. In some embodiments, step 4904 includes collecting data from a smart appliance using digital communications such as a TCP/IP protocol (e.g., using UDP or TCP packets).

At step 4906, the system (e.g., controller 4812) collects data from one or more sensors (e.g., sensors 4850). For example, controller 4812 may receive signals from one more of sensors 4850 at a predetermined frequency, as events or conditioned are sensed, in response to a query, at any other suitable time or schedule, or any combination thereof. In some embodiments, the system may receive information from residential sensors (e.g., of sensors 4850) using direct analog measurement, digital communications (e.g., RS485, TCP/IP, CANbus, modbus), any other suitable signal type, or any combination thereof. The sensors may include, for example, smoke detectors, carbon monoxide (CO) detectors, air quality sensors, particulate sensors, barometers, ambient light sensors, temperature/humidity sensors, water flow sensors and/or leak detectors, microphones, IR and other photosensors, occupancy sensors (e.g., acoustic or optical sensors), any other suitable sensor, or any combination thereof.

At step 4908, the system (e.g., controller 4812) detects, identifies, or otherwise determines a fault or event based on steps 4902, 4904, 4906, or a combination thereof. In some embodiments, the system may use machine learning algorithms, signal processing, frequency-domain analysis (e.g., Fourier analysis), templates or reference information, any other suitable technique, or any combination thereof to detect a fault or event. For example, in some embodiments, the system may compare data from steps 4902, 4904, and/or 4906 with a database, model, or other reference information to identify a fault. For example, if a signal corresponding to a measurement, calculated value based on the signal, output of a machine learning model using signals as an input, or any other suitable determined value exceeds a threshold (e.g., that may be stored in memory as reference information), the system may determine a fault exists or otherwise an event has occurred, is occurring, or is about to occur (e.g., is imminent). In a further example, the system may gather and store data received at steps 4902, 4904, and/or 4906, and apply machine learning to the historical data set (e.g., which may be used at least in part as a training set) to identify characteristics of faults or events that may be used to identify faults or events in real time. In a further example, as data is received (e.g., a time series of values), the system may perform statistical calculations (e.g., maximums, minimums, means, variances, moments, offsets), frequency analysis (e.g., identifying activity of interest in particular frequency bands, low pass or high pass filtering, wavelet analysis), templates that include features (e.g., steps, drifts such as monotonic increases/decreases, oscillations, or other patterns in the data), any other suitable analysis, or any combination thereof.

At step 4910, the system (e.g., controller 4812) causes an action in response to the fault or event. In some embodiments, controller 4812 may automatically mitigate a fault by, for example, using a rule system to determine the appropriate response to faults, taking into account data from additional sensors, taking into account metadata about house and appliances installed therein, taking into account any other suitable information, or any combination thereof. In some embodiment, controller 4812 may implement a trained model to determine an appropriate response. For example, controller 4812 may respond to faults by activating actuators at step 4923; sending commands to connected appliances at step 4922; notifying the user (e.g., homeowner) at step 4912 through visual (e.g., LED, screen) or audio indicators (e.g., speakers, alarms) or network communications (e.g., push notifications, SMS messages, phone calls); notifying a central monitoring entity at step 4914 through network communications; any other suitable actions; or any combination thereof.

At step 4912, the system (e.g., controller 4812) generates and transmits a notification via a suitable communications interface. In some embodiments, if a fault is detected, controller 4812 determines a type of available or preferred communication to use to notify the homeowner. Controller 4812 may also notify personnel of a central monitoring entity of the fault, at step 4914. Controller 4812 may also respond automatically to the fault at step 4920 (e.g., of which steps 4921-4923 are examples). In some embodiments, step 4912 may include generating a display or an indicator on an existing display indicative of the fault. In some embodiments, the notification may be transmitted to a user device (e.g., user device 4350) to alert a user of the fault condition. To illustrate, step 4912 need not include any automatic fault mitigation but rather notify a user who then may take an action or otherwise address the fault. The notification may be communicated using audio (e.g., an audible alert such as an alarm, beeping, or automated voice), visual (e.g., a display, an LED), mobile push notifications (e.g., a text message, smartphone notification, or email), a call (e.g., to a mobile phone), any other suitable type of communication, or any combination thereof. In some embodiments, the system may generate a notification to the user and request input or a selection to confirm whether a detected condition is of concern or is already known to the user. For example, the system may generate a query on a display asking the user if they are participating in any activity that would increase temperature or particulate (e.g., cooking) or washing a particular region (e.g., which may affect humidity or leak detection sensors).

At step 4914, the system (e.g., controller 4812) generates and transmits an alert or otherwise notification to a remote entity. In some embodiments, the remote entity may include power managing entity or panel managing entity that monitors panel activity and may be trained to responds to faults or malfunctions (e.g., the panel installer). In some embodiments, the remote entity may include an emergency response entity such as a fire department, police station, any other suitable emergency responders, or any combination thereof. In some embodiments, the system may generate a notification to the entity and request input or a selection to confirm whether a detected condition is of concern or is already known to the entity. For example, the system may generate a query on a display asking the entity to confirm the detected fault or event. In some embodiments, steps 4912 and 4914 may be combined, performed simultaneously, or otherwise performed in a similar manner. In some embodiments, the system is configured to identify power issues (e.g., based on reference information) for a building or a plurality of buildings. For example, the controller or a plurality of controllers (e.g., corresponding to homes in a neighborhood) may be configured to identify larger scale power issues at step 4908 and generate a notification for a utility indicative of the issue.

At step 4920, the system (e.g., controller 4812) causes an actuation or otherwise automatically mitigates the fault. In some embodiments, the system may identify the fault at step 4908, and identify a corresponding response at step 4910. Step 4920 may include generating and transmitting a control signal based on the response to one or more devices, actuators, or a combination thereof. For example, in some embodiments, the system may input a fault identifier into a lookup table or other database and determine a corresponding response at step 4910. The system may then generate the control signal based on the output. In some embodiments, at step 4920, the system applies fault-response heuristics to determine possible course of automated action. For example, the system may access a set of logical instructions (e.g., a logic tree and reference information) for selecting a response based on a fault type, device identifier, user preference, or combination thereof. In some embodiments, a response for each identified fault or fault type may be predetermined such that, when a fault is detected, the system can select the predetermined response (e.g., which may include any of steps 4912, 4914, and/or 4920).

At step 4921, which is an example of step 4920, the system (e.g., controller 4812) generates and transmits a control signal to one or more relays to disconnect a device associated with the fault. For example, the system may cause a branch relay to open, thus electrically disconnecting a branch circuit from the AC busbars of electrical panel 4811. In some embodiments, the system may generate a control signal for one or more controllable breakers of a branch circuit associated with the faulted device. In some embodiments, the system may disconnect one or more branch circuits corresponding to loads nearby or otherwise having a suitable nexus to a faulted device but which are not themselves faulted. For example, if the system detects a fault associated with a device located in a room, the system may disconnect the faulted device and one or more other circuits or devices in the same room (e.g., if the event is a fire, arc, or other event that may be expected to damage nearby equipment).

At step 4922, which is another example of step 4920, the system (e.g., controller 4812) may generate and send a control signal to one or more smart appliances. For example, the smart appliance may be configured to managing shutdown based on the control signal. In some embodiments, the system may avoid disconnecting an entire branch circuit by implementing step 4922, and causing only the smart appliance to change operation. In some embodiments, the system may generate a plurality of control signals, corresponding to a plurality of smart appliances or devices, to cause each to shut down (e.g., a faulted device or other device having a nexus to the detected event), turn on (e.g., a vent fan), change operation (e.g., lessen consumption or current draw, reduce operating temperature, increase ventilation), enter a safer operating mode, or a combination thereof. The control signal may include a digital signal (e.g., RS485, CANbus, TCP/IP), for example, communicated over a wired connection or a wireless connection (e.g., a WiFi transceiver, Bluetooth).

At step 4923, which is another example of step 4920, the system (e.g., controller 4812) may generate and transmit one or more control signals to other actuators or devices. In some embodiments, the other actuators or devices may be electrically couple to dedicated branch circuits, and the system may actuate relays associated with those circuits. In some embodiments, the system may generate and transmit a control signal to one or more actuators using wiring other than branch circuits (e.g., dedicated wiring or communications wiring). For example, step 4923 may include the system actuating sprinklers, water valves, alarms, fans, pumps, windows or vents, lights (e.g., emergency lighting), speakers, locks (e.g., to secure areas, devices, or otherwise access to devices), any other suitable actuator types, or any combination thereof. In some embodiments, a plurality of actuators or devices having actuators may be networked with controller 4812, and controller 4812 may generate suitable control signals to one or more of the actuators or device based on the fault or fault type.

In an illustrative example, at step 4908, the system may detect hardware failures such as HVAC starting-capacitor degradation, low or leaking refrigerant, motor failures, motor stalls, motor winding shorts, blocked fans, clogged filters, soft shorts (e.g., including tracking/carbonization through plastics or resin, additional conduction paths from humidity, salt, or corrosion, or other suitable behavior), arcs, flickering in lights, bulb failure or burn out imminent (e.g., incandescent, halogen, fluorescent), any other suitable failure, or any combination thereof. The system may generate a notification or alert at step 4912 and/or 4914, and may also disconnect the device by actuating a relay on the corresponding branch circuit at step 4921.

In an illustrative example, at step 4908, the system may detect incorrect usage such as operating devices for too long (e.g., a duration beyond a threshold or specified time period or window), beyond their capabilities of the device (e.g., excessive motor load, excessive current), operating appliances unattended that require attention, operating humidity-sensitive devices in bathrooms, any other usages that may be of concern, or any combination thereof.

In an illustrative example, at step 4908, the system may identify a fault, which may, at step 4912 and/or 4914 automatically trigger a data upload to central monitoring servers including high-resolution electrical signatures, metadata from other sensors in the house, logs from the device, and metadata about the model, and data representing the model's state at the time of firing (e.g., at the time of fault detection). For example, controller 4812 may observe different levels of data collection “verbosity,” analogous to software log levels, in which more “verbose” data collection levels collect data more frequently and/or include additional signals in telemetry uploads. In a further example, controller 4812 may increase its log level due to fault detections and/or assessments of the probability of a fault.

FIG. 50 is a flowchart of illustrative process 5000 for managing fault response, in accordance with some embodiments of the present disclosure. In some embodiments, process 5000 represents an example of process 4900 or otherwise a similar process as process 4900, performed by controller 4812, for example.

At step 5002, the system (e.g., controller 4812) receives a notification or signal from one or more sensors (e.g., similar to step 4906). For example, the system may receive a notification from a smart smoke alarm via a network connection, indicating smoke is detected.

At step 5004, the system (e.g., controller 4812) determines current draw for one or more sensors exceeds a threshold (e.g., based on a measurement similar to step 4902), or otherwise exhibits a feature (e.g., based on a time series of measurements). At step 5004, the system may identify a value (e.g., exceeding a threshold), or a pattern of values (e.g., an excursion, step change, drift or ramp, oscillation, or other suitable feature) that indicate a potential event. For example, referencing a smoke alarm, if current draw of the smoke alarm exceeds a threshold, the system may determine that the audio alarm is activated (e.g., based on a current measurement rather than a communications signal).

At step 5006, the system (e.g., controller 4812) receives sensor signals from one or more other sensors (e.g., similar to step 4906). For example, the one or more other sensor signals may be indicative of one or more events, conditions, changes, or a combination thereof. In a further example, in the context of a fire or other thermal event, the other sensors may include temperature sensors, particulate sensors, or other suitable sensors that indicate a sudden change, sharp increase, or otherwise a reading indicative of an event (e.g., an increasing temperature may indicate fire or fire risk, increased particulate ma indicate smoking, smoldering, or fire).

At step 5008, the system (e.g., controller 4812) detects an event based on steps 5002, 5004, and 5006 (e.g., similar to step 4908). For example, the system may determine a fire is detected based on a signal and/or current draw from a smoke alarm, temperature measurements, particulate measurements, an event detection heuristic, or a combination thereof. For example, once a hazard is detected, controller 4812 may deploy actuators in order to mitigate this hazard, and generate notifications indicative of the hazard.

At step 5010, the system (e.g., controller 4812) generates one or more notifications based on the event and notification preference information. For example, similar to steps 4912 and 4914 of process 4900, the system may notify a homeowner, building manager, panel managing entity, any other entity, or any combination thereof based on detection of the event at step 5008.

At step 5012, the system (e.g., controller 4812) determines a response based on the event. For example, in addition to notifying users and/or remote entities, the system may generate a notification for one or more response entities. Response entities may include local police, local fire department, medical services, local emergency services, any other suitable entities trained to respond, or any combination thereof. In some embodiments, the system may determine whether to notify emergency response entities, and which emergency responders to notify based on the type of event detected at step 5008. In some embodiments, the system determines whether metadata indicates a smoke alarm model that is monitored. For example, if a smoke alarm is registered with a local fire department, then the system may be configured to generate and transmit a notification to the local fire department indicative of a fire or fire-like event (e.g., excessive smoke detected).

At step 5014, the system (e.g., controller 4812) decides to notify an emergency response entity, or alternatively at step 5016, the system decides not to notify an emergency response entity. The determination of whether to alert an emergency response entity may be based on the event or type of event. For example, if the event is fire related, the system may generate a notification at step 5014, while for other faults or events the system may proceed to step 5018 (e.g., not generating the notification via step 5016). In some embodiments, the system may proceed through step 5016 to check for, or otherwise avoid, redundant notifications being sent (e.g., to an emergency response entity).

At step 5018, the system (e.g., controller 4812) identifies one or more appliances, circuits (e.g., branch circuits), or a combination thereof that indicate an excess current draw or other sign of fault or behavior associated with the detected event. The system may identify the circuits and/or devices based on current draw, predetermined links between identified fault types and devices, preferences, locations of devices, mappings of branch circuits to devices, or any other suitable criteria. At step 5018, the system may identify a subset of branch circuits, devices, or both, that are associated with the event and that may be turned off or otherwise undergo modified operation. In some embodiments, the system may determine whether any appliances or devices in an adjoining area or otherwise related to the event exhibit excess current draw or other signs of arcing or an electrical short (e.g., based on measurements received at step 5004).

At step 5020, the system (e.g., controller 4812) disconnects the identified appliances and/or circuits of step 5018. For example, the system may generate one or more control signals to actuate or de-actuate branch relays or controllable breakers to disconnect branch circuits from AC busbars. In a further example, the system may generate and transmit a control signal to one or more smart appliances to turn off, modify operation, or otherwise respond to the event. To illustrate, if an appliance's electrical current signature indicates potential catastrophic failure, controller 4812 may cut power to that appliance (e.g., using a branch relay associated with the appliance).

In an illustrative example, controller 4812 may perform sensor fusion between a plurality of sensors to detect hazards in a house and to increase confidence in the readings of those sensors, as part of processes 4900 and 5000.

In an illustrative example, if an electrically powered sensor (e.g., a smoke alarm) exhibits no current draw or a current draw that is anomalous, as determined at step 5004, controller 4812 may indicate to the user a need for service. If an electrically powered sensor shows current draw consistent with having detected a fault (e.g., increased current draw to a smoke alarm corresponding to turning on its internal loudspeaker), controller 4812 may interpret that as a fault even if the sensor fails to communicate the fault over digital communications.

In an illustrative example, if a fire is observed through a smoke alarm (e.g., step 5002 or 5004) and controller 4812 observes anomalous current draw (e.g., via current sensors 4814) to particular electrical appliances or circuits, controller 4812 may use electrical relays to interrupt the flow of current to those devices (e.g., at step 5020). To illustrate, disconnecting the flow of current may help interrupt an electrical fire. Similarly, if an electrical short, arc, or other abnormality is detected at step 5008, controller 4812 may interrupt current (e.g., via one or more branch relays) in order to interrupt the fire. To illustrate, controller 4812 may detect fires using elevated temperature readings from temperature sensors, increased particulate readings from air quality sensors, signals from a cameras, signals from an infrared (IR) sensor, a signal from a microphone, signals from any other suitable devise, or any combination thereof.

In an illustrative example, controller 4812 may detect human occupancy through electrical current flow to lighting or appliances in addition to occupancy sensors (e.g., occupants generally turn on lights when occupying a room) at step 5004. To illustrate, if the user has registered themselves as away and controller 4812 detects human activity in the house, controller 4812 may actuate speakers, lights, or other suitable appliances such as window blinds in order to deter potential thieves.

In an illustrative example, if a water leak is detected, controller 4812 may interrupt the flow of water to that part of the house by controlling a water valve (e.g., based on a predetermined mapping of locations of sensors and water conduits). In a further example, if a water leak is detected, controller 4812 may disconnect branch circuits extending to the region associated with the water leak to prevent shorting.

In some embodiments, controller 4812 may act to prevent propagation of hazards through the home or facility using processes 4900 or 5000. In some embodiments, for example, an energy management system includes controller 4812 and one or more electrical meters connected to branch circuits in a building. Controller 4812 may collect and store information about appliances, such as their make and model, date of manufacture, size, capacity, rating from users by means of a user interface (e.g., mobile app, touchscreen, etc.), consumption, schedules, notifications, or any other suitable information provided in any suitable manner. For example, controller 4812 may collect and store information about which branch circuits feed each appliance. In some embodiments, controller 4812 provides feedback to users (e.g., homeowners, facility managers) through a user interface. If multiple appliances are connected to a single branch circuit, controller 4812 may use disaggregation algorithms to decompose the measured current draw from the branch circuit into separate current draws per appliance.

FIG. 51 shows two plots illustrating electrical signatures (e.g., power draw) of user behavior, in accordance with some embodiments of the present disclosure. Panel 5100 illustrates electrical behavior corresponding to a first room (e.g., “ROOM 1” which may be an office) and panel 5150 illustrates electrical behavior corresponding to a second room (e.g., “ROOM 2” which may be a bedroom). Controller 4812 may be configured to recognize behavioral patterns corresponding to rooms, regions, users, devices or a combination thereof (e.g., based on features of one or more signals). For example, controller 4812 may be configured to recognize “going to bed” from component electrical signatures. In panel 5100, “EVENT 1” may correspond to a desktop PC entering sleep mode, while “EVENT 2” may correspond to lights being turned off. In panel 5150, “EVENT 3” may correspond to overhead lights being turned on (e.g., wired to a known branch circuit of electrical panel 4811), “EVENT 4” may correspond to a lamp being turned on (e.g., a lamp plugged into an outlet of a known branch circuit of electrical panel 4811), “EVENT 5” may correspond to the overhead lights being turned off, and “EVENT 6” may correspond to the lamp being turned off. The combination of EVENTS 1-6 may be associated with “going to bed” or “sleeping mode” by controller 4812. Controller 4812 may categorize the event using heuristic rule systems, regular expressions, machine learning models, any other suitable technique, or any combination thereof. In some embodiments, the controller may be configured to recognize behavioral patterns corresponding to rooms, regions, users, and devices, as well as pattern corresponding to faults, events, or hazards. For example, for each appliance the controller is monitoring, the controller may use a database of fault signatures, machine learning models, or a combination thereof in order to identify hardware failures, misbehaviors, incorrect usage, or other faults in appliances. The controller may also use anomaly detection algorithms (e.g., including thresholds, rates, or other references) to detect incorrect use or faults not included in the controller's database or training set. In some embodiments, controller 4812 may extract information from one, more than one, some, or all time-series data and any other suitable data to determine features that may then be used to identify the events.

As illustrated in FIGS. 48-51 , the methods and system of the present disclosure may be directed to fault detection and response for a wide variety of potential issues. Illustrative examples of fault detections and/or responses are discussed below.

In some circumstances, controller 4812 may detect that an air conditioner's filter is clogged through a gradual change in fan blower current draw (e.g., at step 5004) and order a replacement to be delivered to the home (e.g., at step 5010).

In some circumstances, controller 4812 may detect that an air conditioner is short-cycling (e.g., based on analyzing current draw over time at step 4902) and prompt the owner to schedule a service appointment (e.g., at step 4912).

In some circumstances, controller 4812 may detect that a sump pump is not operational (e.g., based on a signal from a water level sensor, humidity sensor, or other suitable sensor), creating risk of water damage to the home, and notify the homeowner (e.g., at step 4912).

In some circumstances, controller 4812 may attempt to ward off thieves by detecting human activity in the home, directly or indirectly, during periods in which the homeowner has reported themselves as away from home, and generate sound, light, or activate other appliances in the house (e.g., at step 4923).

In some circumstances, controller 4812 may detect an appliance failure at step 4908 that might lead to fire and/or electrical damage to other appliances and disconnect power to the failing appliance at step 4921 or step 4922.

In some circumstances, controller 4812 may generate and send notifications to the homeowner at step 4912 or 5010 when non-networked sensors such as a smoke detector go off by measuring a difference in their power draw at step 4902 or 5004.

In some circumstances, controller 4812 may detect that an HVAC system is not operating properly by detecting power consumption by the system that are uncorrelated with, or differently correlated from usual (e.g., at step 4902 or 5004) to, changes in temperature and/or humidity measured in the home.

In some circumstances, controller 4812 may detect appliances left on longer than usual that may be hazardous, such as a space heater or oven, and notify the homeowner at step 5010, disconnect power at step 5020, or both.

In some circumstances, controller 4812 may detect the presence of fire by means of temperature and/or particulate matter sensors by comparing the signals from the sensors to reference information such as thresholds.

In some circumstances, controller 4812 may, at step 4906, detect a flow of water to an appliance using a flow sensor, liquid level sensor, humidity sensor, or any other suitable sensor or combination of sensors, that is not operational per the appliance's power draw (e.g., as measured at step 4902), thus indicating a potential leak or other malfunction.

In some circumstances, controller 4812 may help prevent the spread of electrical fires by (i) monitoring a fire using a smoke alarm at step 4906, (ii) localizing the fire to a particular electrical appliance or circuit through observation of elevated or otherwise anomalous current draws or the characteristic signature of an electrical arc or short (e.g., as determined based on measurements of step 4902), (iii) using electrical relays to interrupt the flow of current to those devices (e.g., at step 4921), or a combination thereof.

In some circumstances, controller 4812 may help prevent the spread of fire by detecting fire (e.g., by means of a smoke alarm at step 4904, 4906, 5002, or 5004) in a room not occupied by people (e.g., as measured by lack of Bluetooth beacon proximity, self-reported “away” status, and/or occupancy sensing as described above) and closing electromechanically actuated doors to that room at step 4923.

In some circumstances, controller 4812 may detect that an appliance such as a space heater or an oven has been left on after the user has gone to bed (e.g., at steps 4902 or 4904), seek confirmation from the user of whether that was intentional (e.g., at step 4908), and, in the case that the user doesn't respond, automatically power off said appliance at step 4921 or 4922.

In some embodiments, the integrated electrical panel of the present disclosure may provide benefits over other systems (e.g., panels without a controller or processing circuitry, networked to sensors and actuators). For example, the methods and systems of the present disclosure may allow for:

-   -   integration of home monitoring with energy management equipment,         which may provide monitoring capability to consumers more         economically than as a standalone product;     -   combination of current measurement with collection of metadata         about appliances and the home, which allows for more specific         assessments and more situational awareness (e.g., a label “Sump         Pump” allows controller 4812 to infer both the expected         operational period and the possible impact of non-operation of         the pump);     -   sensor fusion of multiple sensor types in the home, which may         also facilitate situational awareness (e.g., allow detection of         appliance failures based on incongruity between water and         electricity usage);     -   occupancy detection from monitoring of electrical activity in         the house; and/or     -   automated fault response to mitigate and/or prevent the         propagation of faults using heterogeneous sensors and actuators.

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to generate device information about a device based on an electrical current measurement from at least one electrical circuit of a plurality of electrical circuits to which the device is coupled. For example, the controller may generate device information based on steps 4902, 4904, and 4906 of process 4900, and store the device information in memory (e.g., memory 4312 of system 4300 of FIG. 43 ). In some embodiments, the controller is configured to determine that an event has occurred based on the device information. For example, device information may correspond to appliance(s) 4340 or device(s) 4380 of system 4300, loads or sources 4530 or 4540 of system 4500, appliances 4820, 4830, and 4840 of system 4800, any other suitable appliances or devices, or any combination thereof. In some embodiments, the controller is configured to cause an action to be performed in response to determining that the event has occurred.

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to cause the action to be performed by determining whether the device is a smart appliance. For example, if the device is a smart appliance, the controller may generate and send a control signal to the device to mitigate the event. In a further example, if the device is not a smart appliance, the controller may actuate a branch relay of the branch circuit to electrically disconnect the device from a busbar of the panel.

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to cause an actuator of a second device to be actuated in response to the event (e.g., at step 4923). For example, the second device may operate independently from the first device. To illustrate, if the system determines a faulted device has caused a fire to start, the system may control a sprinkler, audio system, or lighting system to mitigate the fire or alert a user to the fire.

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to receive a sensor signal from at least one sensor communicatively coupled to the control circuitry. For example, the controller may receive the sensor signal at step 4902, 4904, or 4906 from current sensors 4814, sensors 4850, or a sensor of or coupled to sensor system 4313. In some embodiments, the controller determines the event has occurred based at least in part on the sensor signal. For example, in the context of a water leak, the sensor may include a humidity sensor, a liquid level sensor, or a leak detector. In a further example, in the context of a detected fire, the sensor may include a smoke detector, a temperature sensor, a particulate sensor, or an optical sensor.

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to communicate with one or more smart appliances (e.g., communicatively coupled to one or more smart appliances). The controller may be configured to receive data from the smart appliance and generate the device information further based at least in part on the data. For example, the controller may store data over time to generate device data (e.g., operating signature, typical current draw, typical operating pattern).

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to determining notification preferences at steps 4912 and 4914, and generate one or more notifications for a user indicative of the event based on the notification preferences. Notification preferences may include an IP address, a phone number, an email address, a user identification, a preferred network or link for sending notifications (e.g., a call, text, email, or application-based notification), or other suitable contact information for reaching a user or entity. In a further example, notification preferences may include a hierarchy or sorted list of users (e.g., an order of notification), priority of notification (e.g., which users are notified first), content of the notification, selectable options to be included in the notification, any other suitable information or settings, or any combination thereof. In some embodiments, the controller is configured to transmit the notification via a communication link based on the notification preferences.

In some embodiments, controller 4812, programmable controller 4525, or control system 4310 is configured to executes instructions stored in non-transitory computer readable medium (e.g., memory 4312). The instructions may include instructions for implementing any or all of processes 4600, 4700, 4900, and 5000, for example.

FIG. 52 is a block diagram of illustrative system 5200 including a plurality of controllers 5210, 5220, 5230, and 5240, and optionally other controllers, in accordance with some embodiments of the present disclosure. For example, system 5200 may be an example of arrangement 2400 of FIG. 24 , where controllers 5210, 5220, 5230, and 5240 may each correspond to one of houses 2401. As illustrated a plurality of controllers are each configured to communicate with each other, backend 5250, device 5260, optionally any other suitable devices, or any combination thereof. For example, each of controllers 5210, 5220, 5230, and 5240 may correspond to a house, and in total, represent an area, set, grouping, or neighborhood. Each of controllers 5210, 5220, 5230, and 5240 may be an EMS or may collectively operate as an EMS. For example, any or all of controllers 5210, 5220, 5230, and 5240 may be configured to monitor a respective electrical panel or system, control aspects of a respective electrical panel or system, store data, transmit data, receive information, generate and transmit notifications, perform any other suitable actions, or any combination thereof. In a further example, as illustrated, controller 5210 is coupled to one or more sensors 5211 and one or more devices 5212, which may include any suitable device receiving or generating electrical power (e.g., appliances, loads, power sources, energy storage devices). In a further example, controllers 5220, 5230, and 5240 may be similarly coupled to respective sensors and devices. In some embodiments, each of controllers of the plurality of controllers (e.g., controllers 5210, 5220, 5230, and 5240) may be configured to monitor and control energy systems. In some embodiments, backend 5250 may be configured to manage aggregate operation (e.g., total consumption) of the plurality of controllers (e.g., controllers 5210, 5220, 5230, and 5240) and may communicate load settings or other suitable information to the plurality of controllers. Device 5260 may include a network device, third-party device, or any other suitable device that may provide information, store information, receive information, analyze information, implement a software application, and communicate information via network to backend 5250, or any or all of controllers 5210, 5220, 5230, and 5240. A system may include a plurality of controllers each configured to monitor current consumption of a respective load or set of loads (e.g., a set of branch circuits or a respective electrical panel), communicate with smart devices/appliances, monitor power generation (e.g., on-site), generate device information, identify a fault or event based on one or more sensor signals (e.g., or features thereof), determine a response to a fault or event, generate and transmit a notification to a user or other entity, actuate one or more devices, perform any other suitable actions, or any combination thereof.

The foregoing is merely illustrative of the principles of this disclosure and various modifications may be made by those skilled in the art without departing from the scope of this disclosure. The above described embodiments are presented for purposes of illustration and not of limitation. The present disclosure also can take many forms other than those explicitly described herein. Accordingly, it is emphasized that this disclosure is not limited to the explicitly disclosed methods, systems, and apparatuses, but is intended to include variations to and modifications thereof, which are within the spirit of the following claims. 

What is claimed is:
 1. A method for managing faults of an electrical system, the method comprising: monitoring power consumption for a plurality of electrical circuits; generating, using processing circuitry, device information about a device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled; determining, using the processing circuitry, that an event has occurred based on the device information; and communicating a control signal to the device in response to the event occurring to mitigate the event.
 2. The method of claim 1, wherein communicating the control signal comprises causing a change in current consumption of the device in response to determining the event has occurred.
 3. The method of claim 1, wherein the at least one electrical circuit comprises a branch circuit of a panel, and wherein communicating the control signal comprises: identifying the device as a smart appliance corresponding to the branch circuit; and generating the control signal based on the device information.
 4. The method of claim 1, wherein the device is a first device, the method further comprising: causing an actuator of a second device to be actuated in response to the event; and the second device operates independently from the first device.
 5. The method of claim 1, further comprising: receiving a sensor signal from at least one sensor communicatively coupled to the processing circuitry; and determining the event has occurred based at least in part on the sensor signal.
 6. The method of claim 1, wherein the device is a smart appliance communicatively coupled to the processing circuitry, the method further comprising: receiving data from the device; and generating the device information further based at least in part on the data.
 7. The method of claim 1, further comprising: determining notification preferences; generating a notification for user indicative of the event based on the notification preferences; and transmitting the notification via a communication link based on the notification preferences.
 8. A system for managing faults, the system comprising: a panel comprising a plurality of electrical circuits; processing circuitry communicatively coupled to a device and configured to: monitor power consumption for the plurality of electrical circuits; generate device information about the device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled; determine that an event has occurred based on the device information; and communicate a control signal to the device in response to the event occurring to mitigate the event.
 9. The system of claim 8, wherein the control signal causing a change in current consumption of the device.
 10. The system of claim 8, wherein the at least one electrical circuit comprises a branch circuit of the panel, and wherein the processing circuitry is further configured to communicate the control signal by: identifying the device as a smart appliance corresponding to the branch circuit; and generating the control signal based on the device information.
 11. The system of claim 8, wherein: the device is a first device; the processing circuitry is further configured to cause an actuator of a second device to be actuated in response to the event; and the second device operates independently from the first device.
 12. The system of claim 8, further comprising at least one sensor coupled to the processing circuitry, wherein the processing circuitry is further configured to: receive a sensor signal from the at least one sensor; and determine the event has occurred based at least in part on the sensor signal.
 13. The system of claim 8, wherein the device is a smart appliance communicatively coupled to the processing circuitry, and wherein the processing circuitry is further configured to: receive data from the device; and generate the device information further based at least in part on the data.
 14. The system of claim 8, wherein the processing circuitry is further configured to: determine notification preferences; generate a notification for user indicative of the event based on the notification preferences; and transmit the notification via a communication link based on the notification preferences.
 15. A non-transitory computer readable medium comprising computer instructions recorded thereon that, when executed, performs a method for managing faults of an electrical system, the method comprising: monitoring power consumption for a plurality of electrical circuits; generating device information about a device based on an electrical current measurement from at least one electrical circuit of the plurality of electrical circuits to which the device is coupled; determining that an event has occurred based on the device information; and communicating a control signal to the device in response to the event occurring to mitigate the event.
 16. The non-transitory computer readable medium of claim 15, wherein the at least one electrical circuit comprises a branch circuit of a panel, and wherein communicating the control signal comprises: identifying the device as a smart appliance corresponding to the branch circuit; and generating the control signal based on the device information.
 17. The non-transitory computer readable medium of claim 15, wherein the device is a first device, and wherein the method further comprises: causing an actuator of a second device to be actuated in response to the event; and the second device operates independently from the first device.
 18. The non-transitory computer readable medium of claim 15, wherein the method further comprises: receiving a sensor signal from at least one sensor communicatively coupled to the processing circuitry; and determining the event has occurred based at least in part on the sensor signal.
 19. The non-transitory computer readable medium of claim 15, wherein the device is a smart appliance, and wherein the method further comprises: receiving data from the device; and generating the device information further based at least in part on the data.
 20. The non-transitory computer readable medium of claim 15, wherein the method further comprises: determining notification preferences; generating a notification for user indicative of the event based on the notification preferences; and transmitting the notification via a communication link based on the notification preferences. 